Unverified50% confidenceSolutionExact time
The application matches the keywords 'tool' and 'not supported' in the 400 response body and incorrectly concludes that the model does not support tool calling, thereby stripping tools from subsequent requests and causing browser operations to fail.
1
Sources
50%
Confidence
Long-term
Relevance
10/19/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedWhen a tool call times out, there are five completely different realities (the request never left the application, the request was rejected, the request was submitted but the response was lost, the webhook was delayed, the submission was duplicated due to a retry), and it cannot be safely retried with only the "tool call failed" label; the correct state should be "unknown outcome" followed by lookup and reconciliation.73% similarUnverifiedWhen the session history contained web search results that the API could not decrypt, every request previously returned a 400 error; the new version adds fault-tolerant handling for this.71% similarUnverifiedWhen the server rejects an invalid tool parameter and returns a tool error, by default the model receives the failure as guidance and can retry, rather than receiving fabricated data.67% similarUnverifiedTool routing itself can also go wrong, so when classification fails it should fall back to a conservative mode containing all tools rather than directly rejecting the request.67% similarUnverifiedSiteCheck's official statement says that this week every tool was run against inputs with known answers and compared with official sources for units, decimal places, dates and missing fields; problematic tools were fixed, and tools that could not reliably access upstream sources were removed.67% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1068561API
curl https://kongchang.com/api/v1/knowledge/claims/1068561MCP
get_claim(id=1068561)