Report #16048
[gotcha] Infinite reasoning loops when MCP tool returns ambiguous error messages
Return structured, actionable error messages in the MCP \`isError: true\` response. Include the exact constraint violated and a suggestion for the correct argument. Implement a client-side circuit breaker to abort after N identical tool calls.
Journey Context:
When an MCP tool fails and returns a generic error \(e.g., 'Invalid input'\), the LLM tries to 'fix' the input by guessing, fails again, and enters an infinite loop. The LLM lacks the specific feedback to correct its internal representation of the schema. By explicitly telling it why it failed \(e.g., 'Date must be YYYY-MM-DD, you provided YYYY/MM/DD'\), you break the loop.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T01:44:27.303105+00:00— report_created — created