Skip to main content
Glama

DNS lookup for a website's domain

dns
Read-only

DNS lookup for a website's domain: A, AAAA, CNAME, MX, NS, TXT and CAA records, via Cloudflare DNS-over-HTTPS. Pass a URL or bare hostname. Fast (under 2 s). Free: 20 calls/day per user across free tools, no payment needed. Above that: $0.002 per call (x402, USDC on Base).

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": {
      "url": "<url>"
    },
    "name": "dns"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Annotations only tell the agent this is a read-only, open-world call. The description adds substantial behavior: sub-2-second latency, a concrete rate limit (20 calls/day free), paid overflow at $0.002/call via x402 USDC on Base, and the fact that an unpaid first call returns price requirements. That is exactly the operational context an agent needs before calling.

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?

Purpose, accepted input, performance, and cost are front-loaded in a single scannable block with no filler. The pricing/payment detail is longer than ideal but is genuinely load-bearing for a paid x402 tool, so it earns its place.

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 read-only lookup with no output schema, the description covers enough to call it correctly: input format, record types, latency, and the payment flow. The one gap is that it never hints at return shape (e.g., per-record-type grouping or empty-result behavior), which an agent might want when parsing results.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it clarifies that the 'url' parameter accepts a bare hostname, which loosens the schema's 'Public http(s) URL' wording and prevents an agent from skipping hostname-only input. The pricing sentence also frames why 'payment' is omitted on the first call.

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 and resource ('DNS lookup for a website's domain') and enumerates the exact record types returned (A, AAAA, CNAME, MX, NS, TXT, CAA), so an agent knows precisely what data comes back. It also names the resolver (Cloudflare DNS-over-HTTPS). It does not explicitly contrast itself with a sibling such as domain_whois, which keeps it 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?

'Pass a URL or bare hostname' gives concrete input guidance and the record-type list implies when the tool is appropriate. However, there is no explicit when-not-to-use guidance or routing to alternatives like domain_whois for registration data, leaving the choice between siblings to inference.

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.