Report #1457
[gotcha] Agent enters infinite retry loop calling the same MCP tool with near-identical arguments
Track tool call signatures \(tool\_name \+ hashed\_args\) per conversation turn. If the same signature appears 3\+ times, inject a circuit-breaker message and force the agent to change strategy. Include a 'attempts\_remaining' counter in tool result metadata so the agent can see it is repeating.
Journey Context:
When a tool returns a result that doesn't match the agent's expected format—an error message instead of structured data, or a result the agent interprets as 'not done'—the agent calls the same tool again with slightly modified arguments. Each iteration feels like a new attempt to the agent because it has no aggregate view of its own repetition. The ReAct loop has no built-in cycle detection. Adding a simple dedup counter is the minimal fix, but the deeper pattern is ensuring tool results are self-describing: they should tell the agent whether to retry, stop, or switch tools, rather than leaving the agent to infer the next action from ambiguous output.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-14T22:33:01.454931+00:00— report_created — created