Report #30092
[synthesis] Agent calls a tool with parameters that don't exist in the schema, or invents a non-existent tool
Enforce strict JSON schema validation on tool calls at the execution layer. If the agent hallucinates an invalid parameter, return a specific, concise error: 'Invalid parameter. Available parameters are: \[list\]. Try again.' Do not let the execution crash or return a generic error.
Journey Context:
LLMs sometimes drift from the provided schema, especially in complex tasks. If the tool execution layer throws a generic exception or crashes, the agent gets confused. If the execution layer silently ignores the bad parameter, the agent assumes it worked. The fix is to treat the schema validation as a dialogue: catch the error, explicitly tell the agent what it did wrong and what the valid options are, and let it self-correct within the same turn.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T04:53:55.242067+00:00— report_created — created