Skip to main content
Glama

reverse_dns

Resolve an IPv4 or IPv6 address to its PTR records and list hostnames pointing back to that IP for DNS reconnaissance and attribution.

Instructions

PTR lookup for an IPv4/IPv6 address (returns hostnames pointing back at the IP).

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": {
      "ip": "<ip>"
    },
    "name": "reverse_dns"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden, and it does disclose the useful part: this returns hostnames mapped back to the IP, implying a read-only lookup. It says nothing about what happens on NXDOMAIN or empty results, whether multiple PTR records can come back, or which resolver is consulted, which is a real gap for a zero-annotation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

One sentence, front-loaded with the operation and followed by the return value — nothing is padded or redundant. The parenthetical is slightly awkward as a container for the return semantics, but it costs the reader nothing.

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

Completeness4/5

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

For a single-parameter lookup with no output schema and no annotations, the essential facts — what it does, what it takes, what it gives back — are all present. The remaining omissions are edge-case behavior (no-record results, multiple answers) that would be nice for an agent deciding how to interpret an empty response.

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 description coverage is 0% and the single 'ip' parameter is documented only as a bare string, so the description must compensate. It does add genuine meaning by stating the parameter accepts IPv4 and IPv6 addresses, which constrains input format beyond the schema, but it offers no syntax examples or invalid-input behavior.

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

Purpose4/5

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

States a specific verb+resource combination ('PTR lookup for an IPv4/IPv6 address') and even names the return ('hostnames pointing back at the IP'), so an agent knows exactly what operation is performed. It stops short of distinguishing itself from the sibling tools 'reverse_ip' and 'dns_lookup', which is the only thing keeping this from a 5.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent can infer that this is the tool to call when it holds an IP and wants a name, but there is no explicit when-to-use framing, no exclusion of 'reverse_ip'/'dns_lookup', and no note on when the forward-lookup siblings would be the better pick.

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