mcp_list
Read-onlyIdempotent
Trade functionality on the cell network: list an MCP server you run (its https url) or one of your...
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| key | No | ||
| url | No | ||
| cell | No | ||
| name | Yes | ||
| what | Yes | ||
| proof | No |
ce-net
by com.ce-net
Schema Changelog
Changes observed during successful MCP inspections.
Changed6 schema fields changed
- removed
Input schema / properties / cell / descriptionRemoved value: -"or a ce-net cell name (like cad.gear) instead of a url" - removed
Input schema / properties / key / descriptionRemoved value: -"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither" - removed
Input schema / properties / name / descriptionRemoved value: -"3-40 of a-z 0-9 . - (like weather.now)" - removed
Input schema / properties / proof / descriptionRemoved value: -"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither" - removed
Input schema / properties / url / descriptionRemoved value: -"your MCP server's https url" - removed
Input schema / properties / what / descriptionRemoved value: -"what it does, its inputs and outputs"
Changed6 schema fields changed
- added
Input schema / properties / cell / descriptionAdded value: +"or a ce-net cell name (like cad.gear) instead of a url" - added
Input schema / properties / key / descriptionAdded value: +"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither" - added
Input schema / properties / name / descriptionAdded value: +"3-40 of a-z 0-9 . - (like weather.now)" - added
Input schema / properties / proof / descriptionAdded value: +"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither" - added
Input schema / properties / url / descriptionAdded value: +"your MCP server's https url" - added
Input schema / properties / what / descriptionAdded value: +"what it does, its inputs and outputs"
Changed6 schema fields changed
- removed
Input schema / properties / cell / descriptionRemoved value: -"or a ce-net cell name (like cad.gear) instead of a url" - removed
Input schema / properties / key / descriptionRemoved value: -"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither" - removed
Input schema / properties / name / descriptionRemoved value: -"3-40 of a-z 0-9 . - (like weather.now)" - removed
Input schema / properties / proof / descriptionRemoved value: -"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither" - removed
Input schema / properties / url / descriptionRemoved value: -"your MCP server's https url" - removed
Input schema / properties / what / descriptionRemoved value: -"what it does, its inputs and outputs"
Changed6 schema fields changed
- added
Input schema / properties / cell / descriptionAdded value: +"or a ce-net cell name (like cad.gear) instead of a url" - added
Input schema / properties / key / descriptionAdded value: +"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither" - added
Input schema / properties / name / descriptionAdded value: +"3-40 of a-z 0-9 . - (like weather.now)" - added
Input schema / properties / proof / descriptionAdded value: +"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither" - added
Input schema / properties / url / descriptionAdded value: +"your MCP server's https url" - added
Input schema / properties / what / descriptionAdded value: +"what it does, its inputs and outputs"
Changed6 schema fields changed
- removed
Input schema / properties / cell / descriptionRemoved value: -"or a ce-net cell name (like cad.gear) instead of a url" - removed
Input schema / properties / key / descriptionRemoved value: -"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither" - removed
Input schema / properties / name / descriptionRemoved value: -"3-40 of a-z 0-9 . - (like weather.now)" - removed
Input schema / properties / proof / descriptionRemoved value: -"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither" - removed
Input schema / properties / url / descriptionRemoved value: -"your MCP server's https url" - removed
Input schema / properties / what / descriptionRemoved value: -"what it does, its inputs and outputs"
Changed6 schema fields changed
- added
Input schema / properties / cell / descriptionAdded value: +"or a ce-net cell name (like cad.gear) instead of a url" - added
Input schema / properties / key / descriptionAdded value: +"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither" - added
Input schema / properties / name / descriptionAdded value: +"3-40 of a-z 0-9 . - (like weather.now)" - added
Input schema / properties / proof / descriptionAdded value: +"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither" - added
Input schema / properties / url / descriptionAdded value: +"your MCP server's https url" - added
Input schema / properties / what / descriptionAdded value: +"what it does, its inputs and outputs"
Changed6 schema fields changed
- removed
Input schema / properties / cell / descriptionRemoved value: -"or a ce-net cell name (like cad.gear) instead of a url" - removed
Input schema / properties / key / descriptionRemoved value: -"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither" - removed
Input schema / properties / name / descriptionRemoved value: -"3-40 of a-z 0-9 . - (like weather.now)" - removed
Input schema / properties / proof / descriptionRemoved value: -"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither" - removed
Input schema / properties / url / descriptionRemoved value: -"your MCP server's https url" - removed
Input schema / properties / what / descriptionRemoved value: -"what it does, its inputs and outputs"
Changed6 schema fields changed
- added
Input schema / properties / cell / descriptionAdded value: +"or a ce-net cell name (like cad.gear) instead of a url" - added
Input schema / properties / key / descriptionAdded value: +"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither" - added
Input schema / properties / name / descriptionAdded value: +"3-40 of a-z 0-9 . - (like weather.now)" - added
Input schema / properties / proof / descriptionAdded value: +"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither" - added
Input schema / properties / url / descriptionAdded value: +"your MCP server's https url" - added
Input schema / properties / what / descriptionAdded value: +"what it does, its inputs and outputs"
Changed6 schema fields changed
- removed
Input schema / properties / cell / propertiesRemoved value: -null - removed
Input schema / properties / key / propertiesRemoved value: -null - removed
Input schema / properties / name / propertiesRemoved value: -null - removed
Input schema / properties / proof / propertiesRemoved value: -null - removed
Input schema / properties / url / propertiesRemoved value: -null - removed
Input schema / properties / what / propertiesRemoved value: -null
Changed12 schema fields changed
- removed
Input schema / properties / cell / descriptionRemoved value: -"or a ce-net cell name (like cad.gear) instead of a url" - added
Input schema / properties / cell / propertiesAdded value: +null - removed
Input schema / properties / key / descriptionRemoved value: -"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither" - added
Input schema / properties / key / propertiesAdded value: +null - removed
Input schema / properties / name / descriptionRemoved value: -"3-40 of a-z 0-9 . - (like weather.now)" - added
Input schema / properties / name / propertiesAdded value: +null - removed
Input schema / properties / proof / descriptionRemoved value: -"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither" - added
Input schema / properties / proof / propertiesAdded value: +null - removed
Input schema / properties / url / descriptionRemoved value: -"your MCP server's https url" - added
Input schema / properties / url / propertiesAdded value: +null - removed
Input schema / properties / what / descriptionRemoved value: -"what it does, its inputs and outputs" - added
Input schema / properties / what / propertiesAdded value: +null
- Added
TDQS
D1.8/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and "list" is consistent with a read operation, so no contradiction. But the truncated description adds essentially no behavioral context such as what the listing returns, visibility rules, or whether it is scoped to your account.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness2/5
Is the description appropriately sized, front-loaded, and free of redundancy?
There is no filler, but that is because the text is truncated mid-sentence rather than deliberately concise. The most important content is missing, which is under-specification, not conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a six-parameter, two-required tool with no output schema and no annotation-level detail on returns, the description should explain the required fields and the two listing modes. It supplies neither, leaving an agent unable to invoke the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% across six parameters, and the description only hints at the url parameter ("its https url"). Required parameters name and what, plus key, cell, and proof, are entirely unexplained, so the description fails to compensate for the schema gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose2/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a verb ("list") and a resource ("an MCP server you run"), but it is truncated mid-sentence ("or one of your..."), leaving the second half of the operation undefined. It also never disambiguates from close siblings like mcp_find, mcp_tools, or mcp_use.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase "or one of your..." gestures at an alternative mode of listing but cuts off before naming it, so no when-to-use guidance or alternative-tool routing survives. An agent gets no condition telling it to pick this over mcp_find.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.