Skip to content

[Bug]: In agent mode, calling the MCP tool fails with a "tool not found" error #13523

@Yuki001

Description

@Yuki001

Note

This issue was translated by Claude.

Issue Checklist

  • I understand that issues are for feedback and problem solving, not for complaining in the comment section, and will provide as much information as possible to help solve the problem.
  • My issue is not listed in the FAQ.
  • I've looked at pinned issues and searched for existing Open Issues, Closed Issues, and Discussions, no similar issue or discussion was found.
  • I've filled in short, clear headings so that developers can quickly identify a rough idea of what to expect when flipping through the list of issues. And not "a suggestion", "stuck", etc.
  • I've confirmed that I am using the latest version of Cherry Studio.

Platform

Windows

Version

1.8.0

Bug Description

In agent mode, there is a problem calling MCP tools, with a prompt indicating the tool cannot be found

Steps To Reproduce

  1. Enable MCP tools (several tools available from Cherry's official options)
  2. Try invoking in the conversation

Expected Behavior

Hope to be able to call tools normally

Relevant Log Output

Additional Context

Attached two rounds of responses from the conversation (since the agent doesn't have full topic export yet, so attaching the responses)

Key points:
```

MCP Tools

Tool Name Purpose
`mcp__U0hLH-rt0xS-5Ud-d0Htl__python_execute` Python Code Execution

Conclusion: `python_execute` exists! It exists as an MCP tool with the full name `mcp__U0hLH-rt0xS-5Ud-d0Htl__python_execute`, supporting execution of Python 3.12 code in a sandbox environment, and can install dependency packages through PEP 723 script metadata.

Deep Thought The user wants to test if the python_execute MCP tool is available and working. Let me try to execute a simple Python program using the MCP tool \`mcp__U0hLH-rt0xS-5Ud-d0Htl__python_execute\`.

The tool call failed. Although the tool appeared available in the previous round of conversation, it is no longer accessible in the current session - this usually happens because the MCP server connection changed or disconnected between sessions.
```

Current Available Tools List.md
Tool Call Failed.md

Image
Original Content

Issue Checklist

  • I understand that issues are for feedback and problem solving, not for complaining in the comment section, and will provide as much information as possible to help solve the problem.
  • My issue is not listed in the FAQ.
  • I've looked at pinned issues and searched for existing Open Issues, Closed Issues, and Discussions, no similar issue or discussion was found.
  • I've filled in short, clear headings so that developers can quickly identify a rough idea of what to expect when flipping through the list of issues. And not "a suggestion", "stuck", etc.
  • I've confirmed that I am using the latest version of Cherry Studio.

Platform

Windows

Version

1.8.0

Bug Description

In agent mode, there is a problem calling MCP tools, with a prompt indicating the tool cannot be found

Steps To Reproduce

  1. Enable MCP tools (several tools available from Cherry's official options)
  2. Try invoking in the conversation

Expected Behavior

Hope to be able to call tools normally

Relevant Log Output

Additional Context

附加上对话中两轮回答(因为暂时agent没有整个话题导出,所以附加上回答)

关键点:
```

MCP 工具

工具名 用途
`mcp__U0hLH-rt0xS-5Ud-d0Htl__python_execute` Python 代码执行

结论:有 `python_execute`! 它以 MCP 工具的形式存在,完整名称为 `mcp__U0hLH-rt0xS-5Ud-d0Htl__python_execute`,支持在沙箱环境中执行 Python 3.12 代码,并可通过 PEP 723 脚本元数据安装依赖包。

已深度思考 The user wants to test if python_execute MCP tool is available and working. Let me try to execute a simple Python program using the MCP tool \`mcp__U0hLH-rt0xS-5Ud-d0Htl__python_execute\`.

工具调用失败了。虽然在上一轮对话中该工具显示为可用,但当前会话中它已不可访问——这通常是因为 MCP 服务器连接在会话之间发生了变化或已断开。
```

当前可用工具列表.md
工具调用失败了.md

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    MCPCategorizes an issue or PR as relevant to SIG MCPneeds-reproneeds to reproduce the bug to figure out

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions