AI & Agent Dev Bug Sandbox Back to Radar

Invalid Tool Call Blocks Are Not Filtered In Langchain-Groq And Langchain-Mistralai V1 Converters

The v1 message converters in langchain-groq and langchain-mistralai do not filter out invalid_tool_call blocks, causing them to be passed to Groq and Mistral APIs. These providers may reject such blocks when replaying partial or malformed tool-call history, leading to runtime errors. Other providers (OpenAI, Anthropic, Fireworks) already filter these blocks.

highConfidence 92%Langchain Affected Vlangchain-Groq<=1.1.3 Affected Vlangchain-Mistralai<=1.1.6

Origin Analysis

Both converters (in langchain_groq._compat._convert_from_v1_to_groq and langchain_mistralai._compat._convert_from_v1_to_mistral) have a catch-all else branch that appends any unrecognized block type to the output. They do not explicitly skip blocks of type 'invalid_tool_call', unlike the converters in langchain_openai, langchain_anthropic, and langchain_fireworks.

1. Install langchain-groq and langchain-mistralai. 2. Create an AIMessage with content blocks including a text block and an invalid_tool_call block, and an invalid_tool_calls list containing that invalid call. 3. Call the respective converter: _convert_from_v1_to_groq(blocks, 'groq') and _convert_from_v1_to_mistral(blocks, 'mistralai'). 4. Observe the output types: openai returns ['text'] while groq and mistralai return ['text', 'invalid_tool_call'].

Fixing Code Block

0x7F 45 4C 46 02 01 01 000x90 12 AB 04 C1 7E 33 08
0xA4 1C 90 3E 77 0B D2 580x11 F6 6A 2C 80 19 DE 44
0x00 00 00 00 03 00 3E 000x01 00 B7 4D 55 90 0C 61
0x6C 69 62 63 2E 73 6F 2E0x36 00 8E 17 42 AA 05 F3
0xDE C0 DE 01 8B 45 FC 890xC7 5D 20 6F 91 03 E4 78
0x13 37 00 4F 9A 2D E1 700x08 B4 5C 22 71 D0 4A 16
0x48 8D 3D 22 01 00 00 E80x91 FF 0A 63 2E 57 B8 04
0x5A 91 C3 0E 44 70 1B 880x02 6F 39 C4 15 80 ED 27
0xFF 15 40 20 60 00 48 890xC3 90 7A 01 4C 28 B1 56
0x0F 1F 44 00 00 55 48 890xE5 C3 18 6D 92 0B 33 A7

Edge Case Audit

This change may drop invalid tool call information from the message history sent to the provider. If the provider can handle such blocks without error in some cases, this could lead to loss of context. Before rolling out, ensure that any legitimate use of invalid_tool_call blocks (e.g., for debugging or introspection) is not impacted. The change is backward-compatible and low-risk; rollback is straightforward by reverting the added skip condition.