fix: prevent MCP tool name collision by prefixing with server name

When multiple MCP servers expose tools with the same name (e.g.,
), selecting one would inadvertently select the other
because both backend registration and the frontend-facing API used
the raw tool name without any server identifier.

Fix:
- MCPTool.__init__: prefix tool name with
  so each tool gets a unique identifier in func_list
- ToolsService.get_mcp_servers: return prefixed names in the
  server info so the frontend can match correctly with availableTools

The actual MCP call still uses the original tool name
(self.mcp_tool.name), so server communication is unaffected.

Author: LiryLee

astrbot/core/agent/mcp_client.py

@@ -686,7 +686,7 @@ def __init__(
         self, mcp_tool: mcp.Tool, mcp_client: MCPClient, mcp_server_name: str, **kwargs
     ) -> None:
         super().__init__(
-            name=mcp_tool.name,
+            name=f"{mcp_server_name}:{mcp_tool.name}",
             description=mcp_tool.description or "",
             parameters=_normalize_mcp_input_schema(mcp_tool.inputSchema),
         )

astrbot/dashboard/services/tools_service.py

@@ -79,7 +79,7 @@ def get_mcp_servers(self) -> list[dict]:
                 for name_key, runtime in self.tool_mgr.mcp_server_runtime_view.items():
                     if name_key == name:
                         mcp_client = runtime.client
-                        server_info["tools"] = [tool.name for tool in mcp_client.tools]
+                        server_info["tools"] = [f"{name}:{tool.name}" for tool in mcp_client.tools]
                         server_info["errlogs"] = mcp_client.server_errlogs
                         break
                 else: