Skip to main content
Glama

dns_zone_transfer

Attempts an AXFR zone transfer against every authoritative nameserver to detect DNS misconfigurations and dump zone records, returning per-server status and up to 300 records on success.

Instructions

Attempt an AXFR zone transfer against every authoritative nameserver.

A successful transfer is a serious DNS misconfiguration and dumps the whole zone. Returns per-nameserver status plus up to 300 records on success.

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": {
      "domain": "<domain>"
    },
    "name": "dns_zone_transfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and does well: it discloses the target set (every authoritative nameserver), the failure/success semantics (per-nameserver status), a truncation cap (up to 300 records), and the security meaning of a hit. It omits rate-limit/IDS-triggering caveats and timeout behavior, which keeps it short of a 5 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.

Conciseness5/5

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

Three short sentences, front-loaded with the action, then the risk interpretation, then the return shape. Nothing is redundant and no filler is present.

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 one-parameter tool with no output schema, the description covers the essential facts: what is attempted, against what, what the response contains, and the 300-record cap. Minor gaps remain around error/timeout reporting and parameter formatting, but an agent could call it correctly after reading this.

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?

There is a single required 'domain' parameter and schema description coverage is 0%, so the description must compensate. 'Against every authoritative nameserver' implies the argument is the zone to enumerate, but it never states the expected format (bare domain vs. FQDN with trailing dot) or whether subdomains are acceptable.

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 opens with a specific verb and resource: 'Attempt an AXFR zone transfer against every authoritative nameserver.' That scope (all authoritative NS, not one resolver) is distinctive enough to distinguish it from siblings like dns_lookup or dns_resolver_compare without reading any schema.

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 only implied. The line 'A successful transfer is a serious DNS misconfiguration' signals that this is an audit/security-check tool, but the description never explicitly says when to prefer this over dns_lookup, nor does it state preconditions such as the target needing a public domain. An agent can infer the context but is not told the alternative.

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