Skip to main content
Glama

x420_dns_lookup

Resolve A, AAAA, MX, TXT, NS, or CNAME DNS records (or all six) for a hostname via the host resolver, returning JSON records, errors, and resolution time.

Instructions

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. PAID: $0.02 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Returns: JSON: name, records{TYPE: []}, errors, resolved_at - the deliverable plus X420's signed receipt and the settlement transaction. Example input: {"name":"example.com","type":"all"}.

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 observedv1.0.2

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses that the call is PAID ($0.02 USDC on Base via x402, drawn from X420_MCP_WALLET_PRIVATE_KEY, 'real money'), which explains why readOnlyHint is false for a lookup. It also states the data source (live DNS via node:dns) and the returned artifact (JSON body plus a signed receipt and settlement transaction), so the agent knows both the cost and the side effects.

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 verb and record types, then payment, then return shape in a logical order, with zero wasted framing. The blanket 'not professional, legal, insurance... advice' disclaimer is boilerplate that does not aid tool selection and slightly dilutes an otherwise dense, purposeful paragraph.

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?

There is no output schema, and the description compensates by naming the return fields (name, records{TYPE: []}, errors, resolved_at) plus the receipt and settlement transaction. Combined with cost, payment path, and data source, an agent has everything needed to decide and invoke correctly for a 2-parameter tool.

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 defines 'name' and 'type' including the 'all' value, and the description largely restates this ('or all six'). The inline example input {"name":"example.com","type":"all"} adds a small amount of concrete usage value, but no format nuances (e.g. trailing dots, IDN handling) are added.

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 (resolves) and a precisely enumerated resource (A, AAAA, MX, TXT, NS, CNAME records for a hostname), plus the resolution mechanism (this host's resolver, node:dns). An agent can tell this apart from registration/domain tools like x420_domain_rdap purely from the record-type list, without inferring from sibling names.

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 by the tool's domain (look up live DNS records for a hostname, use type=all for all six) and the 'Source: live DNS' note clarifies the data provenance. However, it gives no explicit when-to-use versus when-not guidance and never routes the agent to a related sibling (e.g. RDAP for registration data, TLS certificate for cert inspection), leaving that to inference.

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