Report #55465
[tooling] Agent hallucinates extra parameters or sends wrong types to MCP tools
Set \`additionalProperties: false\` in the tool's JSON Schema and mark parameters as required explicitly. Use \`enum\` arrays for constrained choices and describe formats in parameter descriptions \(e.g., 'ISO 8601 date'\). Never leave schema objects open-ended.
Journey Context:
LLMs invent parameters they believe might be helpful when schemas are permissive. \`additionalProperties: false\` forces the model to adhere strictly to the declared contract, reducing hallucination by 60-70% in practice. Enums constrain the output space to valid tokens, while explicit required arrays prevent the model from omitting critical fields. This pattern shifts the burden from the agent's prompt engineering to the server's schema validation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T23:35:28.055873+00:00— report_created — created