Tool call format not being parsed correctly by Cline (VS Code extension)

#24
by sunislee - opened

Hi, I'm running the GGUF version (UD-Q4_K_XL) locally via LM Studio, and trying to use it with Cline (the agentic coding extension for VS Code).

The model correctly understands the task and attempts to call tools, but it outputs the tool call in this format:

list_filespath/Users/xxx

Cline doesn't recognize this as a structured tool call — it just prints the raw text, then the model repeats the same call again in the next turn (since it never gets a tool result back), and after a few retries Cline throws "repeated tool call failures."

Questions:

Is this the intended/standard tool-call output format for Laguna-S-2.1?
Is there a recommended chat template or client configuration that makes this compatible with Cline specifically?
I noticed a discussion (#22, "Very Impressed - 270/270 in my tool usage") mentioning successful tool usage — would appreciate knowing what client/setup was used there for comparison.

Thanks!

Same

I actually had this issue with the model hosted via llamacpp but NOT with the same model hosted via LMStudio (Q4_K_M).
Turns out cline used a much shorter system prompt for LMStudio, which the model could handle well. Have you tried using the "compact system prompt"? With that the model was quite usable through cline. Unfortunately this option doesn't seem to exist for llamacpp.

I am not sure if somebody still has this problem, but laguna was struggling a lot with CLINE, only printing XML formatted tool calls - while it worked just fine with OpenWebUI and other models worked well with CLINE.

I solved this by explicitly defining the model name (poolside/Laguna-S-2.1-NVFP4) in the cline "Open AI compatible" setup page. I usually leave that entry empty, since I am switching models quite a bit, but as soon as I specified the model like this, laguna was finally able to call tools just fine also in CLINE.

FWIW, I've been running Laguna-S-2.1 through OpenCode (via the oh-my-opencode/OMO plugin) with LM Studio as the backend, and tool calls have been working correctly — structured JSON calls, no issue with XML/raw text output. Might be worth trying if you're stuck with Cline.

Sign up or log in to comment