6 views
-/https://github.com/berriai/litellm/issues/28358
GitHub · issue

#28358 Llama 4 Maverick/Scout on Bedrock: tool calling fails with "provider rejected the request schema or tool payload"

  • State: open
  • Author: @khskwok
  • Labels: llm translation

## Environment - LiteLLM version: 1.85.0 - Model: `us.meta.llama4-maverick-17b-instruct-v1:0` (cross-region inference profile) - Provider: AWS Bedrock Converse API - LiteLLM config: bedrock/converse/us.meta.llama4-maverick-17b-instruct-v1:0

## Steps to reproduce 1. Configure LiteLLM proxy with llama4-maverick via bedrock/converse/us.meta.* 2. Send a request that includes any tool/function definition 3. Request fails immediately before the model generates any output

## Error LiteLLM returns HTTP 500 with: `litellm.APIConnectionError: BedrockException - {"Message":"..."}`

The calling application (OpenClaw) reports: `FailoverError: LLM request failed: provider rejected the request schema or tool payload.`

## Root cause hypothesis Bedrock enforces strict JSON Schema draft 2020-12 validation on tool definitions for Llama 4 cross-region inference profiles. The tool schema format LiteLLM sends for openai-completions-compatible tool calls may not pass Bedrock's validation.

Interestingly, Nova models (amazon.nova-micro-v1:0) accept the same tool definitions without issue — this appears specific to Llama 4 cross-region inference profiles.

## Expected behavior Tool calls should work wi…

GitHub resolver

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

Refresh page
vote history (5 events)
#0 of 0 · 31d18h43m2s ago — entered · #import:https:::github.com:berriai:litellm post #2166
The heartbeat feature is harder because it affects asynchronous streaming lifecycles, deployment configuration, connection timing, and proxy compatibility, requiring broader integration and regression testing. The other change is more narrowly scoped to provider-specific request translation and validation.
Issue #28358 is harder because it requires diagnosing and adapting provider-specific tool-schema translation for Bedrock Llama 4, with compatibility testing across model variants and request formats. Issue #32249 is comparatively localized to cookie path handling alongside SERVER_ROOT_PATH.
The right-hand issue is harder because it involves provider-specific schema translation, strict validation behavior, and tool-calling compatibility across Bedrock model variants; the left-hand issue is comparatively narrower and likely localized to identifier normalization or validation.
The right issue has broader provider-specific schema translation and validation risk, while the left issue appears narrower and more localized to request-parameter handling.
#0 of 0 · 31d17h44m56s ago — current · #import:https:::github.com:berriai:litellm post #3138
Model omitted braces; inferred difficulty from issue scope and surface area.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search