@skydiveai/pi-extensions 0.1.0-beta.2103 → 0.1.0-beta.2104

package/dist/index.mjs

@@ -1400,6 +1400,57 @@ function mcpResultToPiContent(result) {
 		text: "MCP tool returned no content."
 	}];
 }
+const MAX_ENUM_VALUES_LISTED = 12;
+function formatEnumValues(values) {
+	const shown = values.slice(0, MAX_ENUM_VALUES_LISTED).map((v) => JSON.stringify(v));
+	if (values.length > MAX_ENUM_VALUES_LISTED) shown.push(`… (${values.length} total)`);
+	return shown.join(", ");
+}
+function extractEnum(propSchema) {
+	if (Array.isArray(propSchema.enum) && propSchema.enum.length > 0) return propSchema.enum;
+	const items = propSchema.items;
+	if (items !== null && typeof items === "object" && Array.isArray(items.enum) && items.enum.length > 0) return items.enum;
+	return null;
+}
+/**
+* Build a compact, human-readable constraint hint from an MCP tool's raw JSON
+* schema so the model sees required fields and each param's allowed enum values
+* inline in the tool description — the schema pass-through hands pi the server's
+* schema verbatim, but the model attends to the prose far more than the raw
+* `enum`/`required` keys. Returns '' when there is nothing worth surfacing.
+*/
+function describeToolConstraints(inputSchema) {
+	if (inputSchema === null || typeof inputSchema !== "object") return "";
+	const schema = inputSchema;
+	const required = Array.isArray(schema.required) ? schema.required.filter((r) => typeof r === "string") : [];
+	const properties = schema.properties !== null && typeof schema.properties === "object" ? schema.properties : {};
+	const enumLines = [];
+	for (const [propName, rawProp] of Object.entries(properties)) {
+		if (rawProp === null || typeof rawProp !== "object") continue;
+		const values = extractEnum(rawProp);
+		if (values) enumLines.push(`- \`${propName}\` must be one of: ${formatEnumValues(values)}`);
+	}
+	if (required.length === 0 && enumLines.length === 0) return "";
+	const lines = ["Argument constraints:"];
+	if (required.length > 0) lines.push(`- required: ${required.map((r) => `\`${r}\``).join(", ")}`);
+	lines.push(...enumLines);
+	return lines.join("\n");
+}
+/**
+* Build the `promptSnippet` a registered MCP tool exposes to the model: the
+* server's description with the argument-constraint hint appended, falling back
+* to a labelled placeholder when the server omitted a description AND the schema
+* carries no constraints (pi's system-prompt builder hides tools whose snippet
+* is empty — system-prompt.js:49). This is the layer where `describeToolConstraints`
+* actually reaches the model, so it is exported and tested directly: the pure
+* hint being correct is necessary but not sufficient; what the model sees is
+* this composed snippet.
+*/
+function buildToolPromptSnippet({ description, inputSchema, serverId }) {
+	const constraintHint = describeToolConstraints(inputSchema);
+	const enriched = constraintHint.length > 0 ? `${description}${description.length > 0 ? "\n\n" : ""}${constraintHint}` : description;
+	return enriched.length > 0 ? enriched : `MCP tool from server "${serverId}".`;
+}
 var McpExtension = class {
 	mcpClients = /* @__PURE__ */ new Map();
 	registeredMcpToolNames = /* @__PURE__ */ new Set();
@@ -1419,7 +1470,11 @@ var McpExtension = class {
 		const name = makeToolName(serverId, tool.name);
 		const parameters = Type.Unsafe(tool.inputSchema);
 		const description = tool.description?.trim() ?? "";
-		const promptSnippet = description.length > 0 ? description : `MCP tool from server "${serverId}".`;
+		const promptSnippet = buildToolPromptSnippet({
+			description,
+			inputSchema: tool.inputSchema,
+			serverId
+		});
 		pi.registerTool(withSummaryStrippedBeforeValidation({
 			name,
 			label: `MCP: ${serverId}/${tool.name}`,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@skydiveai/pi-extensions",
-  "version": "0.1.0-beta.2103",
+  "version": "0.1.0-beta.2104",
   "homepage": "https://skydive.com",
   "license": "MIT",
   "author": "Create, Inc.",