Report #71339
[tooling] Agent hallucinates non-existent parameters when calling MCP tools
Set \`additionalProperties: false\` in the tool's JSON Schema inputSchema and enumerate all valid properties explicitly
Journey Context:
By default, JSON Schema permits extra properties not defined in \`properties\`. LLMs frequently hallucinate plausible but incorrect parameter names \(e.g., \`file\_name\` instead of \`filename\`\). When the schema is permissive, these hallucinations pass validation and reach the tool implementation, causing runtime errors or silent failures. Setting \`additionalProperties: false\` forces strict validation at the protocol level, causing the MCP client to reject the call immediately. This triggers the LLM to retry with corrected parameters based on the explicit schema definition, significantly reducing tool call error rates.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T02:19:21.211273+00:00— report_created — created