The model frequently makes mistakes in specifying the instrument name when calling it; it constantly indicates use_mcp_tool instead of the specific name available in the instrument.
I compared the original prompt to what was obtained after processing.
Original:
## use_mcp_tool
Description: Request to use a tool provided by a connected MCP server. Each MCP server can provide multiple tools with different capabilities. Tools have defined input schemas that specify required and optional parameters.
Parameters:
- server_name: (required) The name of the MCP server providing the tool
- tool_name: (required) The name of the tool to execute
- arguments: (required) A JSON object containing the tool's input parameters, following the tool's input schema
Usage:
<use_mcp_tool>
<server_name>server name here</server_name>
<tool_name>tool name here</tool_name>
<arguments>
{
"param1": "value1",
"param2": "value2"
}
</arguments>
</use_mcp_tool>
Example: Requesting to use an MCP tool
<use_mcp_tool>
<server_name>weather-server</server_name>
<tool_name>get_forecast</tool_name>
<arguments>
{
"city": "San Francisco",
"days": 5
}
</arguments>
</use_mcp_tool>
And here is a very poor description after processing, and there is a bug here - the instrument name is incorrect; I even had to create an issue because this revealed a bug in the roo code.
## use_mcp_tool
Usage:
use_mcp_tool.server name here.use_mcp_tool arguments: {"param1": "value1", "param2": "value2"}
Example: Requesting to use an MCP tool
use_mcp_tool.weather-server.use_mcp_tool arguments: {"city": "San Francisco", "days": 5}
Here, the instrument name get_forecast is lost (there is also no description).
The model frequently makes mistakes in specifying the instrument name when calling it; it constantly indicates use_mcp_tool instead of the specific name available in the instrument.
I compared the original prompt to what was obtained after processing.
Original:
And here is a very poor description after processing, and there is a bug here - the instrument name is incorrect; I even had to create an issue because this revealed a bug in the roo code.
Here, the instrument name get_forecast is lost (there is also no description).