Skip to main content
Glama

x402 Tool Shop

DNS Lookup + Mail Policy

dns_lookup
Read-only

DNS lookup for any domain: A, AAAA, MX, NS, TXT, CNAME, CAA and SOA records in one call, plus the domain's email DNS (SPF and DMARC policy) read out plainly. Or ask for one record type. Resolved live through three public resolvers with automatic fallback. Price: $0.003 USDC per call (x402). Free sample: call free_sample with tool="dns_lookup".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dns_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOptional single record type: A, AAAA, MX, TXT, NS, CNAME, CAA, SOA
domainNoDomain name, e.g. example.com (a URL is accepted; the host is used)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds real behavioral context: resolution is live through three public resolvers with automatic fallback, and each call costs $0.003 USDC via x402. What's still absent is failure behavior (NXDOMAIN, resolver disagreement, partial results) and output shape, which matters for a tool that can return up to nine record categories.

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 front-loaded sentences: capability, optional narrowing, then resolution method and pricing. Every sentence carries information, though the pricing/free-sample commercial tail is marginally less relevant to invocation decisions than the resolver and record-type details.

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?

With no output schema, the description must convey what comes back — it does, stating that SPF and DMARC are "read out plainly" and that all record types can be returned in one call. Combined with pricing, resolver behavior, and the free-sample route, an agent has everything needed to call this correctly.

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. The description earns a point by clarifying the default mode — omitting `type` returns all record types plus SPF/DMARC — which the schema only implies by calling `type` "Optional". It also restates the accepted URL-instead-of-host convenience.

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?

Names a specific verb and resource ("DNS lookup for any domain") and enumerates the exact record types (A, AAAA, MX, NS, TXT, CNAME, CAA, SOA) plus SPF/DMARC policy extraction. An agent can tell this apart from email_check or free_sample 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 Guidelines4/5

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

Explicitly covers both modes — all records in one call, or "ask for one record type" — and points to the free_sample sibling for a no-cost trial. It stops short of stating when NOT to use it (e.g. when a validated email/policy verdict is needed, as with email_check), but the usage context is clear.

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