shodan_query_listList shared community search queries with pagination and sorting by votes or timestamp so you can discover and reuse Shodan search filters.
List shared community search queries.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| sort | No | ||
| order | No |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The only added behavioral signal from the description is that results are community-shared rather than private, which is a modest but real contribution beyond structured fields.
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 front-loaded sentence with no filler, which is structurally clean. However, the brevity reflects under-specification rather than tight economy given three undocumented parameters.
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?
No output schema exists, so the description should convey what a returned query looks like and how pagination behaves, and it does neither. For a listing tool with three unannotated parameters, the definition leaves out information an agent needs to call it correctly.
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% for three parameters, so the description should compensate, but it never mentions page, sort, or order. Even the enum choices (votes/timestamp, asc/desc) are left for the agent to discover in the raw schema without any explanation of defaults or effect.
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 gives a specific verb and resource ("List shared community search queries"), and the qualifier "shared community" distinguishes it from the personal/saved-query sibling shodan_query_search. It stops short of explicitly naming that sibling, but the scope is clear enough to identify the tool.
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 statement of when to use this instead of shodan_query_search or shodan_query_tags, and no mention of prerequisites or pagination context. The agent must infer usage entirely from the one-line purpose.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.