Skip to main content
Glama

Dns records

dns_records
Read-onlyIdempotent

Live DNS lookup for A, AAAA, MX, NS, TXT, CNAME, CAA and SOA records of a public domain. $0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYespublic domain name, e.g. example.com
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, openWorld, idempotent, non-destructive), yet the description still adds the two facts an agent cannot get elsewhere: a per-call price of $0.001 and the accepted payment rails (x402, USDC on Arc/Base/Solana, XNT on X1). The two-phase sign-then-pay flow is disclosed up front, which is exactly the behavioral context a paid tool needs.

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 sentences, each doing distinct work: capability and record types first, price and rails second, invocation flow third. No filler, no restatement of the title, and the most decision-relevant information is front-loaded.

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?

No output schema exists, so the description carries some burden for return expectations; it enumerates the queryable record types but says nothing about response shape (per-type records, NXDOMAIN/error behavior). Payment cost, rails, and the auth flow are all covered, so what remains is a minor gap rather than a blocking one.

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 schema already defines both parameters and the baseline is 3. The description earns above baseline by explaining the sequencing relationship between the two calls — the first returns terms, the second carries the signed payload — which the schema alone does not convey.

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?

Opens with a specific verb and resource — 'Live DNS lookup for A, AAAA, MX, NS, TXT, CNAME, CAA and SOA records of a public domain' — which is far more precise than a generic 'get DNS'. It never names a sibling, so an agent must infer for itself whether email_security (which likely also surfaces MX/SPF/DMARC data) is the better fit.

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

Usage Guidelines4/5

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

Gives explicit conditional guidance for the payment parameter: 'Call once without `payment` for the terms, sign them with your own wallet, call again with `payment`.' That is a clear two-step invocation recipe. It stops short of saying when to prefer this tool over overlapping siblings such as email_security or tls_cert, and offers no exclusions.

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