Report #45439
[gotcha] Agent enters a retry loop because the MCP server rejects tool arguments with extra hallucinated parameters
Ensure the MCP server tool schemas explicitly define additionalProperties: false and the client catches the JSON Schema validation error, feeding the exact schema violation back to the LLM to correct the parameters.
Journey Context:
LLMs frequently hallucinate extra parameters or guess types. If the MCP server schema doesn't strictly forbid extra properties, it might silently ignore them, causing subtle bugs later. If it does reject them but the client just returns a generic 'tool failed' error, the LLM repeats the mistake. The fix is strict schemas plus precise error feedback so the LLM self-corrects.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T06:44:33.546621+00:00— report_created — created