OpenClaw "Model Does Not Support Tools" Error: What It Means and How to Fix It

Your model can chat fine. It just can't call tools. Here's why, and which models actually work.

Quick answer: The "model does not support tools" error in OpenClaw means your Ollama model wasn't trained for function calling. Fix it by switching to a tool-capable model and pointing your config at the native Ollama API (no /v1 in the URL):

# Pull a tool-capable model
ollama pull qwen3-coder:30b   # or hermes3, gemma4, mistral:7b for lighter options

# In your OpenClaw config, ensure the Ollama provider uses the native API:
#   provider: ollama
#   baseUrl: http://127.0.0.1:11434     (NOT http://127.0.0.1:11434/v1)
#   models: [qwen3-coder:30b]

# Restart and verify
openclaw doctor --deep

If you're on OpenClaw with Ollama 0.17+, ollama launch openclaw --model qwen3-coder:30b does the same setup as a single command.

The rest of this post explains what's happening, which other models work, and how to choose between them.

You installed Ollama. You pulled phi3:mini because it's small and fast. You connected it to OpenClaw. You asked your agent to search the web.

And then: "Model does not support tools."

Your model loaded. Your gateway started. Chat works perfectly. But the moment your agent tries to use a skill, execute a command, or call any tool, this error kills the interaction.

Here's what it means and exactly how to fix it.

What "model does not support tools" actually means

Tool calling is a specific capability that not every language model has. When your OpenClaw agent needs to search the web, check your calendar, or read a file, it doesn't do those things directly. It generates a structured request (a "tool call") that tells OpenClaw which tool to use and what arguments to pass. OpenClaw then executes the tool and sends the results back to the model.

The problem: generating structured tool calls is a skill the model has to be trained for. A model that's great at conversation might never have been trained to output tool call syntax. When OpenClaw sends a request with available tools to a model that doesn't understand tool calling, the model either ignores the tools entirely or throws the "model does not support tools" error.

This isn't an OpenClaw bug. It's not a config problem. Your model genuinely can't do what you're asking it to do. It's like asking a calculator to play music. The hardware works. It just wasn't built for that function.

"Model does not support tools" means exactly what it says. Your model wasn't trained for function calling. Switch to one that was.

The models that trigger this error

These Ollama models are commonly used with OpenClaw and commonly trigger the "does not support tools" error:

phi3:mini (3.8B) is the most frequent offender. It's popular because it's tiny and runs on almost any hardware. But it has no tool calling support. It will chat all day. It will never call a tool.

qwen2.5:3b and other small quantized models frequently lack tool calling support. Below 7B parameters, tool calling capability is rare.

Unmodified base models without instruction tuning or tool-specific training. If the model's Ollama page doesn't mention "tool calling" or "function calling" in its capabilities, it won't work for agent tasks.

Older model versions that predate tool calling support. Even models that now support tools may have older versions on Ollama that don't. Make sure you're pulling the latest version.

For the complete list of recommended models for OpenClaw, our Ollama troubleshooting guide covers which models work, which don't, and the hardware requirements for each.

The models that actually support tool calling

The community-recommended stack for OpenClaw + Ollama in 2026:

qwen3-coder:30b is the current community favorite for tool-heavy agent work (30.5B params / 3.3B active MoE, 256K native context). At aggressive quantization it fits on a 24GB GPU; full precision needs ~250GB memory. Pull with ollama pull qwen3-coder:30b.

glm-4.7-flash is the other pillar of the local stack — 30B-A3B MoE, ~19GB at q4_K_M, requires Ollama 0.14.3+. Strong reasoning, tool-call format is reliable. Pull with ollama pull glm-4.7-flash.

qwen3.5:9b and gemma4:e4b are the lightweight tool-capable picks for 16-24GB machines. Both released in 2026 and both train explicitly on tool-call format.

gpt-oss:20b (OpenAI's open-weights release, MXFP4-quantized, runs on 16GB) and hermes3 are the other entry-level options. Note that the previous-generation hermes-2-pro is no longer the official Hermes — Ollama's library now lists hermes3.

mistral:7b still works and remains in Ollama's official tool-calling recommendations, but its reasoning ceiling is lower than the 2026 options.

Switch your OpenClaw config to one of these. Use the exact name + tag (qwen3-coder:30b with the colon, not a hyphen). Restart the gateway. The "does not support tools" error should be gone.

Model compatibility at a glance

Native API vs /v1: the real cause of tool-call failures

Stay with me here. If you've switched to a tool-capable model and tool calls still fail silently — the agent narrates what it would do instead of calling tools — your config is pointing at the wrong endpoint.

For most of early 2026, OpenClaw routed Ollama requests through the OpenAI-compatible /v1 path with streaming enabled. Ollama's /v1 streaming implementation drops tool-call delta chunks (the bug tracked in GitHub Issue #5769). The model generates the tool call. The /v1 streaming pipeline drops it. OpenClaw never sees it.

OpenClaw's native Ollama provider uses /api/chat instead and preserves tool calls under streaming. The official Ollama provider docs explicitly warn against using /v1 because it still breaks tool calling. If your config has this:

ollama:
  baseUrl: "http://localhost:11434/v1"    # broken: drops tool calls

Change it to this:

ollama:
  baseUrl: "http://localhost:11434"       # native /api/chat, tool calls work

Then update OpenClaw to a recent release and run openclaw doctor --deep to verify.

So the full diagnostic order for "my agent can't call tools":

1. Are you on a tool-capable model? (See the table above.)
2. Is your baseUrl pointing at the native API (no /v1)?
3. Is OpenClaw recent enough to use the native Ollama provider by default?

If yes to all three, tool calls work. If you're stuck on an older OpenClaw build that can't be updated, the community workaround is to disable streaming when tools are present (covered in our troubleshooting guide).

How to check before you try

Before pulling a new Ollama model for OpenClaw, check whether it supports tool calling. Two quick ways:

Check the Ollama model page. Go to the model's page on ollama.com. Look for "tools" or "function calling" in the capabilities or description. If it's not mentioned, the model probably doesn't support it.

Check the model's Modelfile. The Modelfile defines the model's capabilities. Models with tool calling support will have tool-related template configurations. If the Modelfile only has a basic chat template, tools aren't supported.

This 30-second check saves you the frustration of pulling a 4GB model, configuring it, testing it, and then getting the "does not support tools" error.

For the broader picture of how Ollama models interact with OpenClaw — including the native vs /v1 distinction, model discovery timeouts, and WSL2 networking issues — our comprehensive Ollama guide covers every failure mode.

The realistic path forward

The short version:

• Seeing "model does not support tools"? Switch to a tool-capable model (table above) and make sure your baseUrl doesn't end in /v1. Both fixes together get tool calls working locally.
• Need an agent without managing model compatibility yourself? BetterClaw ships $19/month per agent, BYOK with 28+ cloud providers — every supported model has working tool calling, no "does not support tools" errors, no endpoint config to debug.
• Need to mix local and cloud? Model routing lets you keep Ollama for heartbeats or privacy-sensitive tasks and route tool-heavy work to a cloud provider.

The managed vs self-hosted comparison covers how these decisions translate across deployment approaches.

Frequently asked questions

What does "model does not support tools" mean in OpenClaw?

The Ollama model you're using wasn't trained for function calling. OpenClaw agents need models that can generate structured tool-call requests for web search, file ops, calendar, skills, and so on. Models like phi3:mini and qwen2.5:3b lack this capability. Switch to a tool-capable model like qwen3-coder:30b, hermes3, or mistral:7b.

Which Ollama models support tool calling for OpenClaw?

Current picks: qwen3-coder:30b and glm-4.7-flash for the 24GB+ tier; qwen3.5:9b, gemma4:e4b, gpt-oss:20b, hermes3, and mistral:7b for 16GB machines. See the compatibility table above. Pair any of these with OpenClaw's native Ollama provider (baseUrl: http://localhost:11434, no /v1) and tool calls work end-to-end.

How do I fix the "model does not support tools" error?

Two-step fix: (1) pull a tool-capable model — ollama pull qwen3-coder:30b is the current default. (2) Make sure your Ollama provider's baseUrl is http://127.0.0.1:11434 with no /v1 suffix; the /v1 path drops tool-call responses even with the right model. Restart the gateway and run openclaw doctor --deep to verify.

Is it worth using Ollama with OpenClaw now that tool calling works?

Yes if you need data privacy, offline operation, or want to offload heartbeats and high-volume tooling from a cloud bill. Cloud APIs still win on reasoning ceiling and per-token latency, so most teams settle on a hybrid: cloud primary, local for privacy-sensitive or high-volume background tasks. The model routing guide covers the setup.

Will the Ollama tool calling issue be fixed in OpenClaw?

It's already fixed in current OpenClaw releases: the native Ollama provider (/api/chat) preserves tool calls under streaming, and it's the default in recent versions. If you're on an older build using the /v1 OpenAI-compatible path, update OpenClaw and switch your baseUrl to drop the /v1 suffix. The "model does not support tools" error itself is unrelated and stays — it only triggers when the model literally wasn't trained for function calling.

Related Reading

• OpenClaw Ollama "Fetch Failed" Fix — Connection errors between OpenClaw and Ollama
• OpenClaw Local Model Not Working: Complete Fix Guide — All local model issues in one guide
• OpenClaw Ollama Guide: Complete Setup — Full Ollama integration from scratch
• Cheapest OpenClaw AI Providers — Cloud alternatives when local models fall short