After updating with ollama version 0.20.1 for fixing gemma4 tool parsing error(#15254), ollama still show errors on tool calling. time=2026-04-04T13:58:18.757+09:00 level=WARN source=gemma4.go:293 msg="gemma4 tool call parsing failed" error="invalid character '' looking for beginning of value" content="call:write{content:\n\n# Project Style Guide for Autonomous Agents' Code Generation (AGENTS.md)\n\nThis document captures the *de facto* coding standards observed across the src/andcomponents/` source code, designed to ensure consistency for all generated code and modules consumed by the agent system. time=2026-04-04T13:57:33.487+09:00 level=WARN source=gemma4.go:293 msg="gemma4 tool call parsing failed" error="invalid character '\'' looking for beginning of value" content="call:grep{include:<|"|>.py<|"|>,output_mode:<|"|>content<|"|>,path:<|"|>/data/robotics/experiment1<|"|>,pattern:':\s\w+'<|"|>}"

TL;DR

The issue with ollama version 0.20.1 showing errors on tool calling after updating for fixing gemma4 tool parsing error may be resolved by properly escaping special characters in the tool call content.

Guidance

• Verify that the content passed to the gemma4 tool call does not contain unescaped special characters, such as backticks or backslashes, which may be causing the parsing error.
• Check the documentation for the gemma4 tool to ensure that the content format is correct and that any special characters are properly escaped.
• Test the tool call with a simplified content string to isolate the issue and determine if the problem is with the content or the tool call itself.
• Consider updating the ollama version or the gemma4 tool to a version that properly handles special characters in the content.

Example

No specific code snippet can be provided without more information about the tool call content and the expected format.

Notes

The provided log output suggests that the issue is with the parsing of special characters in the tool call content. However, without more information about the expected format and the tool call content, it is difficult to provide a more specific solution.

Recommendation

Apply workaround: Properly escape special characters in the tool call content to prevent parsing errors. This is a safe and reasonable approach given the information provided in the issue.