Skip to main content
Glama

Sitesy Website Intelligence

DNS records

dns_lookup
Read-onlyIdempotent

The full DNS record set for one domain: A, AAAA, CNAME, MX, NS, TXT, SOA, CAA. Costs 0.002 USDC per call. The caller pays per call in USDC on Base through x402: the first call returns the payment requirements, and an x402 aware MCP client signs and retries automatically.

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

Input Schema

NameRequiredDescriptionDefault
domainYesA domain name, for example example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds genuinely non-obvious behavior: a concrete price (0.002 USDC per call) and the x402 payment handshake, where the first call returns payment requirements and the client must sign and retry. That payment-retry loop is exactly the kind of operational detail an agent needs to avoid treating the first response as a failure.

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?

Three short sentences, front-loaded with scope and record types before cost and payment mechanics. Every sentence carries information; minor density in the x402 sentence but nothing extraneous.

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 simple, single-parameter read tool, the description covers scope, returned record types, and the payment prerequisite. Since there is no output schema, more detail on the per-record result shape (TTL, values) would have helped, but the essentials an agent needs to call it correctly are present.

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?

One parameter with 100% schema description coverage, so the schema already documents 'domain' with an example and length bounds. The description adds only the framing 'for one domain', which does not meaningfully extend the schema — baseline 3 applies.

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+resource ('full DNS record set for one domain') and enumerates exactly which record types are returned (A, AAAA, CNAME, MX, NS, TXT, SOA, CAA), which is far more informative than the title 'DNS records'. It stops short of distinguishing itself from sibling dns_posture, so an agent must infer the split.

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 scope statement ('full record set for one domain'), but there is no explicit when-to-use/when-not guidance and no routing to alternatives such as dns_posture or domain_profile. Adequate but leaves selection 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.

Resources