# witcheer's Wingtips #23: pointed Hermes at your own model and it prints the tool call instead of running it?

Written by [witcheer](https://x.com/witcheer) at Nous Research. Republished with credit.

Canonical: https://hermeswatcher.com/wingtips/23  
Published: 2026-07-17  
[Original](https://notwitcheer.github.io/hermes-recipes/wingtips/23-pointed-hermes-at-your-own-model-and-it-prints-t/) · [On X](https://x.com/witcheer/status/2078094918740758606) · [Full collection](https://notwitcheer.github.io/hermes-recipes/) · [Official docs](https://hermes-agent.nousresearch.com/docs/integrations/providers)

[Source Markdown](https://raw.githubusercontent.com/notwitcheer/hermes-recipes/8653fb699a137a32e81936fa33cabacd3f4f2095/docs/wingtips/23-pointed-hermes-at-your-own-model-and-it-prints-t.md): use this file as the base for relative links in the verbatim text below.

Sources: [Hermes docs: Providers](https://hermes-agent.nousresearch.com/docs/integrations/providers)


Hermes Wingtips #23: pointed Hermes at your own model and it prints the tool call instead of running it?

if the reply comes back as raw json like {"name": "web_search", ...}, your inference server handed the tool call over as text and Hermes never got to run it.

tool calling has to be switched on at the server, and it is off until you set it:

(1) vLLM: add --enable-auto-tool-choice --tool-call-parser hermes

(2) SGLang: add --tool-call-parser qwen (or your model's parser)

(3) llama.cpp: add --jinja