{"version":"2.1.228","anchor":"unparseable-tool-call-json-gives-a-clear-error-instead-of-br","canonical_anchor":"unparseable-tool-call-json-gives-a-clear-error-instead-of-br","heading":"Unparseable tool-call JSON gives a clear error instead of breaking the stream","tier":"notice","area":"Tool Calls","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/unparseable-tool-call-json-gives-a-clear-error-instead-of-br","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Unparseable tool-call JSON gives a clear error instead of breaking the stream\n\nBroken tool-call JSON now gives you a readable error instead of killing the response.\n\n**What**\n\nWhen the model emits tool input JSON that will not parse, the failure is caught while streaming, the input is replaced with an empty object, and you get a readable message quoting the bad JSON rather than the stream blowing up.\n\n**Details**\n\n- Caught at both the incremental delta and the end of the content block.\n\n**Evidence**\n\n`Unable to parse tool parameter JSON from model. Please retry your request or adjust your prompt.`\n\n- Area: Tool Calls\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}