Skip to main content
Glama

dns_audit

Detect whether a target's DNS service permits open recursion and retrieve its NSID, helping identify resolver exposure and misconfiguration risks.

Instructions

Check whether a target's DNS service allows open recursion and expose its NSID.

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": {
      "target": "<target>"
    },
    "name": "dns_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It discloses the core operation, checking open recursion and exposing NSID, which implies a read-only DNS query, but it does not state that the operation is non-destructive, what access is required, or how the NSID is returned.

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 focused sentence with no wasted words, and the core operation is front-loaded. It is appropriately sized for a simple one-parameter audit tool.

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

Completeness3/5

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

The tool is simple and an output schema exists, so the description need not explain return values. However, with no annotations and no parameter description coverage, it remains underspecified on target format and safety properties, which matters for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description should compensate for the single 'target' parameter. It clarifies that the target is a DNS service, but does not specify whether the value should be an IP address, hostname, domain, or another format.

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?

The description uses a specific verb, 'Check,' and names the exact DNS behaviors: open recursion and NSID exposure. This clearly distinguishes it as the DNS-focused audit tool among the protocol-specific audit siblings, though it does not explicitly mention alternatives.

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

Usage Guidelines2/5

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

The description gives no explicit when-to-use guidance, prerequisites, or exclusions. Usage is only implied by the tool name and the mention of a DNS service, leaving the agent to infer when this audit is appropriate versus other audit tools.

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