Skip to main content
Glama

DNS records for a domain

domain_dns
Read-only

Current DNS records for a hostname from Cloudflare DNS over HTTPS: A, AAAA, CNAME chain, MX with priority and null-MX flag, NS, TXT (up to 25 records of at most 400 characters, email addresses redacted), CAA as flag, tag and value, and SOA primary nameserver, serial and timers, each with its minimum TTL. An optional type parameter limits the answer to one record type. For subdomains without their own zone, NS and SOA come from the registrable domain. Price: $0.003 per successful call, paid in USDC with x402 v2; failed calls and calls that match nothing are not charged.

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": "domain_dns"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOne record type to return instead of all of them (case-insensitive).
domainYesBare domain, hostname, email address or URL. Scheme, path, port and credentials are stripped and IDNs are converted to punycode. IP addresses and private names are rejected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses material behavior: TXT capped at 25 records of 400 characters with email addresses redacted, pricing at $0.003 per successful call via x402 v2, and no charge for failed or empty-match calls. That is genuine value-add the annotations cannot convey. It stops short of explaining how payment is presented or what an auth failure looks like, keeping it below a 5.

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?

Front-loaded with the resource and return shape, and the pricing caveat is a useful closing sentence. The main return-value sentence is very long and dense with comma-separated enumeration, but nearly every clause carries information an agent cannot get elsewhere.

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?

With no output schema, the description carries the burden of describing return values and does so thoroughly per record type, plus billing and redaction behavior. The gap is the payment mechanics: it names x402 v2 and USDC but does not say how a call is paid for or which sibling handles that, leaving an agent to discover it.

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 100%, so the enum-bound type parameter and the domain normalization rules (scheme/path/port stripping, punycode, IP and private-name rejection) are already fully documented in the schema. The description only restates that type limits the answer to one record type, adding no syntax or format detail beyond the schema, so the 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?

States a specific verb and resource ("Current DNS records for a hostname from Cloudflare DNS over HTTPS") and enumerates exactly what is returned, including per-type detail like MX priority/null-MX flags and CAA flag/tag/value. The explicit record-type list plus the subdomain NS/SOA fallback rule make it unmistakable versus siblings such as domain_whois or domain_email_auth.

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 directed: the description explains that the optional type parameter narrows results and how subdomain queries behave, which tells an agent what the tool does at call time. However, it never says when to prefer this over sibling tools (domain_report, domain_email_auth, domain_whois) or that x402_preflight/x402_receipt relate to its payment flow, so the agent must infer routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources