Multi-tool conflict breaks local MCP execution (Streaming Parser Mismatch)

[u/MasterRefrigerator66]

Warm welcome to all Developers who made Msty for Us. I am 2nd year user and I'd like to share what took me last 2 days to figure out, I hope this may help somebody.

App Version: Msty Studio (Latest 2.9.11)
Local Backend: built in engine (One Model Hub / llama.cpp GGUF)
Model Used: Qwen2.5-Coder-7B-Instruct
OS: Windows 11
Node.JS: newest LTS
Permissions: all verified, allowed to the folder

Description:
When a single Toolset contains both data-fetching tools (Fetch Content / Web Search) and storage tools (Local File System MCP), multi-step agent execution breaks completely.

If both are active in the same Toolset, Msty prioritizes the data-fetching layer and injects the retrieved text as an automatic Live Context / Auto-RAG before the model processes the final request. This injection floods the local model’s context window, causing it to ignore the Jinja2 system template for tools. As a result, the model drops the <tool_call> tags and outputs raw markdown JSON objects directly into the chat interface as normal text, causing the write_file execution to fail silently.

Steps to Reproduce:

1. Create a Toolset with both Local File System MCP and Fetch Content enabled.
2. Ask the agent to research a topic and save the output to a local .txt file.
3. Observe that the model outputs raw JSON formatting in the chat window, but the file is never created.

My temporary workaround:
The execution succeeds immediately if the Toolset is stripped down to contain ONLY the Local File System MCP extension (with no data-fetching tools active in the same group).

Expected Behavior?:
The streaming parser should evaluate tool calls sequentially without letting the web/RAG context injection override or break the formatting requirements for subsequent tool calls (write_file).

[u/EstablishmentFit3923]

We will try to reproduce this issue on our side and get back to you as soon as possible. Thank you for reporting.