List the most recent scan results across MCP servers taken from the official registry, with verdicts and issue counts.
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "list_scan_results"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| verdict | No | optional filter |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the behavioral disclosure burden. It adds useful context: results are recent, sourced from the official registry, and include verdicts and issue counts. However, it does not mention default limit behavior, pagination, or whether the operation is purely read-only, though 'list' strongly implies it.
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?
A single well-structured sentence that front-loads the primary purpose and then adds relevant qualifiers ('most recent', 'official registry', 'verdicts and issue counts'). There is no filler or redundant repetition of the tool name.
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 simple read-oriented listing tool with two optional parameters and no output schema, the description covers the essential context: what is listed, from where, in what order, and what the results contain. It is not fully complete because it omits default limit semantics and any routing guidance relative to `check_mcp_server`, but those are minor gaps.
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 50%: `verdict` is documented as an optional filter and has an enum, while `limit` has no description. The description mentions 'most recent' and 'verdicts' but does not explicitly explain the `limit` parameter or how it interacts with the verdict filter, so it only partially compensates for the coverage gap.
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 states a specific action ('List'), a precise resource ('most recent scan results across MCP servers taken from the official registry'), and the output content ('verdicts and issue counts'). The plural bulk-list framing naturally distinguishes this from the singular sibling `check_mcp_server`, though it does not name that alternative explicitly.
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?
There is no explicit guidance about when to use this tool versus `check_mcp_server`, nor any exclusions or prerequisites. The description merely implies a bulk listing operation, leaving the agent to infer the appropriate choice from the tool names alone.
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.