mcp_use
Call one tool on a public MCP server through ce-net and get its answer.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| key | No | ||
| url | Yes | ||
| tool | Yes | ||
| proof | No | ||
| arguments | No |
Call one tool on a public MCP server through ce-net and get its answer.
| Name | Required | Description | Default |
|---|---|---|---|
| key | No | ||
| url | Yes | ||
| tool | Yes | ||
| proof | No | ||
| arguments | No |
Changes observed during successful MCP inspections.
Input schema / properties / arguments / descriptionRemoved value: -"the tool's arguments, at most 32 KB"Input schema / properties / key / descriptionRemoved value: -"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"Input schema / properties / proof / descriptionRemoved value: -"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"Input schema / properties / tool / descriptionRemoved value: -"a tool name from mcp_tools"Input schema / properties / arguments / descriptionAdded value: +"the tool's arguments, at most 32 KB"Input schema / properties / key / descriptionAdded value: +"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"Input schema / properties / proof / descriptionAdded value: +"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"Input schema / properties / tool / descriptionAdded value: +"a tool name from mcp_tools"Input schema / properties / arguments / descriptionRemoved value: -"the tool's arguments, at most 32 KB"Input schema / properties / key / descriptionRemoved value: -"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"Input schema / properties / proof / descriptionRemoved value: -"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"Input schema / properties / tool / descriptionRemoved value: -"a tool name from mcp_tools"Input schema / properties / arguments / descriptionAdded value: +"the tool's arguments, at most 32 KB"Input schema / properties / key / descriptionAdded value: +"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"Input schema / properties / proof / descriptionAdded value: +"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"Input schema / properties / tool / descriptionAdded value: +"a tool name from mcp_tools"Input schema / properties / arguments / descriptionRemoved value: -"the tool's arguments, at most 32 KB"Input schema / properties / key / descriptionRemoved value: -"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"Input schema / properties / proof / descriptionRemoved value: -"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"Input schema / properties / tool / descriptionRemoved value: -"a tool name from mcp_tools"Input schema / properties / arguments / descriptionAdded value: +"the tool's arguments, at most 32 KB"Input schema / properties / key / descriptionAdded value: +"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"Input schema / properties / proof / descriptionAdded value: +"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"Input schema / properties / tool / descriptionAdded value: +"a tool name from mcp_tools"Input schema / properties / arguments / descriptionRemoved value: -"the tool's arguments, at most 32 KB"Input schema / properties / key / descriptionRemoved value: -"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"Input schema / properties / proof / descriptionRemoved value: -"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"Input schema / properties / tool / descriptionRemoved value: -"a tool name from mcp_tools"Input schema / properties / arguments / descriptionAdded value: +"the tool's arguments, at most 32 KB"Input schema / properties / key / descriptionAdded value: +"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"Input schema / properties / proof / descriptionAdded value: +"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"Input schema / properties / tool / descriptionAdded value: +"a tool name from mcp_tools"Input schema / properties / arguments / propertiesRemoved value: -nullInput schema / properties / key / propertiesRemoved value: -nullInput schema / properties / proof / propertiesRemoved value: -nullInput schema / properties / tool / propertiesRemoved value: -nullInput schema / properties / url / propertiesRemoved value: -nullInput schema / properties / arguments / descriptionRemoved value: -"the tool's arguments, at most 32 KB"Input schema / properties / arguments / propertiesAdded value: +nullInput schema / properties / key / descriptionRemoved value: -"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"Input schema / properties / key / propertiesAdded value: +nullInput schema / properties / proof / descriptionRemoved value: -"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"Input schema / properties / proof / propertiesAdded value: +nullInput schema / properties / tool / descriptionRemoved value: -"a tool name from mcp_tools"Input schema / properties / tool / propertiesAdded value: +nullInput schema / properties / url / propertiesAdded value: +nullDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds only that the call goes through ce-net and returns an answer; it does not explain side effects, authentication via key/proof, or error behavior for an open-world invocation tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The single sentence is front-loaded and contains no filler. It is efficient, though very sparse for a complex invocation tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a five-parameter, open-world tool that invokes arbitrary remote MCP tools, the description is far too thin. Annotations cover the safety profile, but the description does not explain required inputs, arguments structure, authentication, or return behavior.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% across five parameters, including a nested arguments object, and the description names none of them. It does not explain url, tool, key, proof, or how arguments should be formatted, so it fails to compensate for the absent schema documentation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb and resource: "Call one tool on a public MCP server through ce-net." It is clear what the tool does, though it does not explicitly distinguish itself from nearby siblings such as mcp_tools, mcp_find, or tool_describe.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It implies usage for calling a tool on a public MCP server, but gives no explicit when-to-use guidance, prerequisites, or alternatives. An agent is not told when to choose this over mcp_tools or mcp_find.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.