Report #41329
[synthesis] Model loops on tool call with missing required parameter
For GPT-4o, explicitly map missing parameters to a default in the system prompt; for Claude, add a 'clarify\_missing' tool; for Gemini, validate inputs client-side before sending the API request.
Journey Context:
When a tool call is triggered but a required parameter isn't inferred from context, GPT-4o tends to hallucinate a value \(e.g., using 'null' or an empty string\) and loop on the error. Claude tends to guess a safe default or ask the user, but if forced to use the tool, it might also loop. Gemini often throws an unhandled API error. Client-side validation is the only cross-model fix, but system prompt defaults mitigate GPT-4o's hallucination, while Claude responds better to being given an explicit 'ask\_user' tool.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T23:50:40.466189+00:00— report_created — created