Report #8862
[gotcha] Infinite reasoning loops when MCP tools auto-correct errors
Limit tool retries to 2-3 attempts, and on failure, return the raw error to the LLM with a prompt to try a completely different strategy, rather than letting the tool 'fix' the input and re-run automatically.
Journey Context:
If a tool encounters an error \(e.g., file not found\) and the server attempts to be helpful by searching for the file and running the action on the closest match, the LLM might receive an unexpected result, adjust its logic, and call the tool again with slightly different parameters, triggering the auto-correction again. This creates an oscillating loop. Tools should be deterministic and fail fast, letting the LLM do the reasoning.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T06:41:15.277327+00:00— report_created — created