@jaypie/mcp 0.8.173 → 0.8.175

package/dist/assets.js

@@ -55,11 +55,11 @@ function getMcpAssetPaths() {
  */
 function getMcpBuildInfo() {
     return {
-        commit: "a6fc7633"
+        commit: "a3ee062e"
             ,
-        version: "0.8.173"
+        version: "0.8.175"
             ,
-        versionString: "@jaypie/mcp@0.8.173#a6fc7633"
+        versionString: "@jaypie/mcp@0.8.175#a3ee062e"
             ,
     };
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jaypie/mcp",
-  "version": "0.8.173",
+  "version": "0.8.175",
   "description": "Jaypie MCP",
   "repository": {
     "type": "git",

package/release-notes/jaypie/1.2.110.md

@@ -0,0 +1,9 @@
+---
+version: 1.2.110
+date: 2026-09-26
+summary: Pulls @jaypie/llm 1.3.51
+---
+
+## Changes
+
+- **`@jaypie/llm` 1.3.51**: `providerOptions` no longer leak to fallback providers; `fallback` entries accept their own `providerOptions` (#591).

package/release-notes/jaypie/1.2.111.md

@@ -0,0 +1,9 @@
+---
+version: 1.2.111
+date: 2026-09-27
+summary: Pulls @jaypie/llm 1.3.52
+---
+
+## Changes
+
+- **`@jaypie/llm` 1.3.52**: Gemini tool declarations no longer send `additionalProperties` and other unsupported JSON Schema keywords (#593).

package/release-notes/llm/1.3.51.md

@@ -0,0 +1,17 @@
+---
+version: 1.3.51
+date: 2026-09-26
+summary: providerOptions reach only the model they were written for; fallback entries carry their own providerOptions; MODEL.FIREWORKS.DEEPSEEK moves to deepseek-v4p1-flash
+---
+
+## Changes
+
+- Per-call `providerOptions` on `operate` and `ocr` reach the primary only, its linger pass included. Previously every fallback received them verbatim, so options shaped for one provider (OpenAI `reasoning`) broke a fallback on another (Gemini rejected `reasoning` in `generation_config`) and the chain provided no resilience (#591)
+- `LlmFallbackConfig` gains `providerOptions`, sent only to that entry
+- Fallbacks derived from a `model` array carry no `providerOptions`
+- `MODEL.FIREWORKS.DEEPSEEK` is now `accounts/fireworks/models/deepseek-v4p1-flash`, the same id as `DEEPSEEK_FLASH`. Fireworks withdrew `deepseek-v4-pro-0813` from serverless (404 "Model not found"); its `COST` entry stays
+
+## Testing
+
+- `npm run test -w packages/llm`: new specs cover operate (cross-provider fallback, per-entry options, linger pass) and ocr scoping
+- Fireworks hot spec passes for every catalog id, deepseek-v4p1-flash included

package/release-notes/llm/1.3.52.md

@@ -0,0 +1,15 @@
+---
+version: 1.3.52
+date: 2026-09-27
+summary: Gemini tool declarations convert parameters to the OpenAPI 3.0 subset, so Zod-derived tool schemas no longer fail with a 400
+---
+
+## Changes
+
+- 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)
+- 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
+- `const` and `$ref` are stripped, as in `responseSchema`; literal and referenced constraints do not reach Gemini
+
+## Testing
+
+- `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

package/release-notes/mcp/0.8.174.md

@@ -0,0 +1,9 @@
+---
+version: 0.8.174
+date: 2026-09-26
+summary: llm skill documents providerOptions scoping across fallback chains
+---
+
+## Changes
+
+- **`llm` skill**: "Provider Options in a Chain" covers per-entry `providerOptions` on `fallback`.

package/release-notes/mcp/0.8.175.md

@@ -0,0 +1,9 @@
+---
+version: 0.8.175
+date: 2026-09-27
+summary: llm skill documents tool schema conversion for Gemini
+---
+
+## Changes
+
+- **`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

@@ -182,6 +182,8 @@ const response = await Llm.operate("What's the weather in NYC?", {
 });
 ```
 
+`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.
+
 ### Built-in Tools
 
 ```typescript
@@ -809,6 +811,23 @@ const response = await Llm.operate(input, {
 });
 ```
 
+### Provider Options in a Chain
+
+`providerOptions` belongs to the model it was written for. Per-call `providerOptions` reach the primary only (including its linger pass); a fallback receives only the `providerOptions` on its own entry, or none. Options shaped for one provider (OpenAI `reasoning`, Gemini `thinkingConfig`) would otherwise break every other provider in the chain. Prefer first-class `effort` and `temperature`, which translate per provider.
+
+```typescript
+const response = await llm.operate(input, {
+  fallback: [
+    {
+      provider: "google",
+      model: LLM.MODEL.GEMINI_FLASH,
+      providerOptions: { thinkingConfig: { thinkingBudget: 1024 } },
+    },
+  ],
+  providerOptions: { reasoning: { summary: "detailed" } }, // primary only
+});
+```
+
 ### Fallback Response Metadata
 
 ```typescript