Skip to main content
Glama

X420 agent services

x420_dns_lookup

Read-onlyIdempotent

DNS lookup: Resolves A, AAAA, MX, TXT, NS or CNAME records (or all six) for a hostname through this host's resolver (node:dns). Source: live DNS. Not professional, legal, insurance, engineering, medical, financial or tax advice. Price: $0.02 USDC per call (x402 on Base). This hosted tool does NOT pay and does NOT return the deliverable: it validates the input and returns payment instructions (pay_to, network, price and the x402 URL to pay at). GET the url; read PAYMENT-REQUIRED from the 402; retry with PAYMENT-SIGNATURE (x402 v2). Or run the local x420-mcp server with your own wallet key to pay automatically. Deliverable once paid: JSON: name, records{TYPE: []}, errors, resolved_at.

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

Input Schema

NameRequiredDescriptionDefault
nameYeshostname, e.g. example.com
typeNoa (default), aaaa, mx, txt, ns, cname or all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the paid x402 flow: the hosted tool does not perform the resolution or return the deliverable, it returns payment instructions, and the caller must GET the url, read PAYMENT-REQUIRED from the 402, and retry with PAYMENT-SIGNATURE. It also names the cost ($0.02 USDC on Base) and the resolver implementation (node:dns), which no annotation conveys.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Front-loaded with the actual capability and dense with genuinely necessary payment mechanics, but the boilerplate 'Not professional, legal, insurance...' disclaimer consumes a full sentence without informing invocation. Long single paragraph rather than clearly separated purpose / payment / output sections.

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

Completeness5/5

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

For a paid hosted tool with no output schema, the description covers the one thing an agent would otherwise get wrong: that a call yields payment instructions rather than DNS records, plus how to complete the paid retry and what the final JSON contains (name, records by type, errors, resolved_at). Nothing essential to calling it correctly is missing.

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 schema already documents both 'name' and 'type'. The only addition is clarifying that 'all' means all six record types, a marginal gain over the schema's own enumeration.

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 ('Resolves A, AAAA, MX, TXT, NS or CNAME records ... for a hostname') with the record-type scope spelled out. An agent can distinguish this from sibling lookups such as x420_domain_rdap or x420_tls_certificate without opening the 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?

The description gives detailed operational context for the payment handshake but never states when to prefer this tool over sibling lookups (domain RDAP, TLS certificate, or local resolver alternatives), nor any exclusions. Usage is implied by the record-type list rather than guided.

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