Unverified50% confidenceSolutionExact time
When an LLM node returns malformed JSON, the tool contract specifies not to retry indefinitely, but instead to log the error, skip that record, and mark the number of skipped records in the summary.
1
Sources
50%
Confidence
Long-term
Relevance
10/16/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedContract drift in tool calls (such as a tool changing from returning plain text to returning JSON, or a schema adding a required field) usually does not directly produce an error pointing to the root cause, but instead manifests as the model repeatedly failing to parse, outputting garbled text, or retrying.78% similarUnverifiedIn streaming LLM APIs, some relay stations silently insert data: [DONE] to end early, or stuff error messages such as {"error": "rate limit exceeded"} into JSON disguised as model answers.78% similarUnverifiedOne of the most common sources of LLMs outputting incomplete JSON is that the model has a maximum output length (max tokens), and once exceeded it is truncated, leaving brackets and quotes unclosed.73% similarUnverifiedWhen FateShow validates the JSON returned by the model, it discards palaces not present in the input, facts not belonging to that palace's star list, and rule ids not output by the rule layer, and backfills missing palaces from the rule-based interpretation by original index.72% similarUnverifiedThe tool should return a clear error message upon blocking (such as "all proxy nodes are currently rate-limited by the target host"), letting the LLM treat the failure as an unrecoverable state and thus switch strategies rather than retry.71% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1047544API
curl https://kongchang.com/api/v1/knowledge/claims/1047544MCP
get_claim(id=1047544)