Zovo IP Lookup

Reverse DNS lookup

reverse_dns_lookup

Read-onlyIdempotent

Use this when the user wants a reverse dns lookup, an ip address lookup for PTR names, or a quick ip lookup of hostnames: it queries DNS-over-HTTPS for the in-addr.arpa or ip6.arpa name of one to twenty public IPv4 or IPv6 addresses and returns host names with a CSV download, without reading a registry. Limits: a PTR name exists only when the network operator sets it; private, loopback, link-local, shared, multicast, documentation and reserved addresses are not queried. Do not use when the user wants the owner, the registration dates or the abuse contact of an address (use lookup_ip for that).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ips": "<ips>"
    },
    "name": "reverse_dns_lookup"
  }
}

Input Schema

Name	Required	Description	Default
`ips`	Yes	One to twenty public IPv4 or IPv6 addresses, separated by commas, spaces, or new lines. Example: 8.8.8.8, 1.1.1.1, 2606:4700:4700::1111.

Output Schema

Name	Required	Description	Default
`count`	Yes
`notes`	Yes
`records`	Yes
`sources`	Yes
`downloads`	Yes
`found_count`	Yes
`preview_note`	Yes
`preview_limit`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare read-only, idempotent, open-world, non-destructive, but the description adds substantial behavior: DNS-over-HTTPS query, no registry read, CSV download return, PTR existence dependency, and excluded address classes. This is useful context 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single well-structured sentence with front-loaded usage guidance, followed by limits and exclusions. Every clause adds value with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a network lookup tool with full schema, rich annotations, and an output schema, the description covers usage, exclusions, limitations, and return format. Nothing critical is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the single 'ips' parameter is fully documented in the schema. The description restates the one-to-twenty public IP constraint but adds no syntax or format details beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('queries DNS-over-HTTPS') and resource ('in-addr.arpa or ip6.arpa name') and explicitly distinguishes from sibling lookup_ip by stating what it does not do. An agent can identify its scope without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides explicit triggers ('Use this when the user wants a reverse dns lookup...'), exclusions ('Do not use when...'), and a named alternative (lookup_ip). Also states query limits and excluded address types.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Zovo IP Lookup tools Inspect

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.

Resources

Need Help?