shodan_dns_domainRetrieve subdomains and DNS records Shodan has indexed for a domain, with optional record type, page, and history filters.
Return subdomains and DNS records Shodan knows for a domain.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| type | No | ||
| domain | Yes | ||
| history | 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 this is a read-only, idempotent, non-destructive, open-world operation. The description adds useful context that results are what 'Shodan knows' rather than live DNS resolution, but it omits pagination behavior and what history=true changes.
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. It is as concise as possible while still stating purpose and scope.
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?
With no output schema and four parameters, the description is too thin: it does not explain pagination, the DNS type filter, or historical results. It also does not clarify the return shape beyond 'subdomains and DNS records'.
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 four parameters, and the description only implicitly covers domain. It does not explain page, type, or history, which are significant for correct invocation.
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?
States a specific verb ('Return') and resource ('subdomains and DNS records') scoped to a domain, so the core purpose is clear. It does not explicitly distinguish itself from DNS siblings such as shodan_dns_resolve or shodan_dns_reverse.
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?
Provides no guidance on when to use this tool instead of the DNS resolve/reverse siblings, nor any prerequisites or exclusions. The only implied usage is that it returns Shodan-known DNS data for a domain.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.