@jaypie/mcp 0.8.174 → 0.8.175

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/assets.js CHANGED
@@ -55,11 +55,11 @@ function getMcpAssetPaths() {
55
55
  */
56
56
  function getMcpBuildInfo() {
57
57
  return {
58
- commit: "6d3baca1"
58
+ commit: "a3ee062e"
59
59
  ,
60
- version: "0.8.174"
60
+ version: "0.8.175"
61
61
  ,
62
- versionString: "@jaypie/mcp@0.8.174#6d3baca1"
62
+ versionString: "@jaypie/mcp@0.8.175#a3ee062e"
63
63
  ,
64
64
  };
65
65
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@jaypie/mcp",
3
- "version": "0.8.174",
3
+ "version": "0.8.175",
4
4
  "description": "Jaypie MCP",
5
5
  "repository": {
6
6
  "type": "git",
@@ -0,0 +1,9 @@
1
+ ---
2
+ version: 1.2.111
3
+ date: 2026-09-27
4
+ summary: Pulls @jaypie/llm 1.3.52
5
+ ---
6
+
7
+ ## Changes
8
+
9
+ - **`@jaypie/llm` 1.3.52**: Gemini tool declarations no longer send `additionalProperties` and other unsupported JSON Schema keywords (#593).
@@ -0,0 +1,15 @@
1
+ ---
2
+ version: 1.3.52
3
+ date: 2026-09-27
4
+ summary: Gemini tool declarations convert parameters to the OpenAPI 3.0 subset, so Zod-derived tool schemas no longer fail with a 400
5
+ ---
6
+
7
+ ## Changes
8
+
9
+ - The Google adapter passes every tool's `parameters` through `jsonSchemaToOpenApi3`, the same conversion `responseSchema` uses. Previously Gemini received the schema verbatim and rejected keywords outside its subset (`additionalProperties`, which `z.toJSONSchema` always emits), failing the request and pushing every call to the fallback provider (#593)
10
+ - Covers user tools, the legacy `structured_output` tool, and the Gemini 3 runtime fallback that rebuilds the request after the native `responseJsonSchema` + tools combo is rejected
11
+ - `const` and `$ref` are stripped, as in `responseSchema`; literal and referenced constraints do not reach Gemini
12
+
13
+ ## Testing
14
+
15
+ - `npm run test -w packages/llm`: new GoogleAdapter specs assert no `$schema`, `$defs`, `$ref`, `additionalProperties`, or `const` reaches any function declaration, across nested `properties`, `items`, and `anyOf`, and that caller schemas are not mutated
@@ -0,0 +1,9 @@
1
+ ---
2
+ version: 0.8.175
3
+ date: 2026-09-27
4
+ summary: llm skill documents tool schema conversion for Gemini
5
+ ---
6
+
7
+ ## Changes
8
+
9
+ - **`llm` skill**: "Define Tools with Toolkit" notes that `z.toJSONSchema` output works as `parameters` and that Google converts tool schemas to Gemini's OpenAPI 3.0 subset.
package/skills/llm.md CHANGED
@@ -182,6 +182,8 @@ const response = await Llm.operate("What's the weather in NYC?", {
182
182
  });
183
183
  ```
184
184
 
185
+ `parameters` is JSON Schema; `z.toJSONSchema(...)` output works directly. Each provider receives a schema it accepts: Google converts tool parameters (and the `structured_output` tool) to Gemini's OpenAPI 3.0 subset, stripping `$schema`, `$defs`, `$ref`, `additionalProperties`, and `const` at every depth. Literal (`const`) and `$ref` constraints do not reach Gemini; spell them out in `description` or `enum` when they matter.
186
+
185
187
  ### Built-in Tools
186
188
 
187
189
  ```typescript