Report #78992
[synthesis] Parsing tool call responses fails due to unsolicited conversational text
Use native tool-calling APIs instead of raw text completion parsing; if using chat completions, explicitly prompt 'Use the tool without any preamble or conversational text' and strip text outside the schema.
Journey Context:
Developers switching from GPT-4o \(which natively outputs structured tool JSON via the API\) to Claude 3 via raw completion endpoints are surprised when Claude outputs 'I will use the search tool now. ...'. This breaks strict JSON parsers. GPT-4o's API handles this natively, but Mistral often outputs specific \`\[BEGIN\_TOOL\_CALL\]\` tags in raw completions. The fix is to use the provider's native tool-calling endpoint \(which abstracts preamble\) or explicitly instruct the model to omit conversational filler, preventing parser crashes.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T15:11:07.292941+00:00— report_created — created