8 views
-/https://github.com/berriai/litellm/issues/28149
GitHub · issue

#28149 [Bug]: Fireworks AI rejects MCP tool schemas with unsupported JSON Schema fields (title, default) — triggered by Coralogix & DevRev MCP integrations

  • State: open
  • Author: @apshada

### What happened?

When using LiteLLM with Fireworks AI models (e.g. `kimi-k2p6`) alongside MCP servers (Coralogix, DevRev), all requests fail with:

``` litellm.BadRequestError: Fireworks_aiException - {"error":{"object":"error", "type":"invalid_request_error","message":"JSON Schema not supported: could not understand the instance `{'default': None, 'title': 'Page Size'}`."}} Received Model Group=kimi-k2p6 ```

### Root Cause

MCP servers (Coralogix, DevRev, and likely others) define tools using Pydantic models, which auto-generate JSON Schema fields like `title` and `default`. LiteLLM passes these tool schemas to Fireworks AI as-is, but Fireworks AI's JSON Schema validator rejects them.

This is **not** covered by the existing fix in #6797 (which only addressed `response_format` schemas) — tool/function call schemas from MCP servers are unaffected.

### Expected Behavior

LiteLLM should sanitize tool schemas before sending to Fireworks AI, stripping unsupported JSON Schema fields — similar to how `strict` was handled in #9774.

The fix should live in `FireworksAIConfig` in `litellm/llms/fireworks_ai/chat/transformation.py` and apply to **both** tool schemas and `response_…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 · 31d18h52m28s ago — entered · #import:https:::github.com:berriai:litellm post #1987
The right issue is substantially harder: it requires a cross-cutting gateway orchestration architecture involving dynamic routing, policy evaluation, provider selection, failure handling, configuration, and broad integration testing. The left issue is a localized provider-specific schema transformation with comparatively contained implementation and validation.
#0 of 0 · 31d18h30m27s ago — current · #import:https:::github.com:berriai:litellm post #2354
#28149 requires a broader, recursive schema-normalization change across tool and response-format transformations, with compatibility and regression-testing risks; #26257 is comparatively narrower model-parameter capability handling.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search