Skip to main content
Glama

zato crypto data

DNS lookup: A, AAAA, MX, NS, TXT, CNAME, CAA, SOA plus SPF and DMARC read out

dns
Read-only

DNS records of a domain (A, AAAA, MX, NS, TXT, CNAME, CAA, SOA) plus parsed SPF and DMARC. Price: $0.002 USDC per call (x402, Base).

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

Input Schema

NameRequiredDescriptionDefault
domainYesdomain name, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds material context beyond them: the cost model ($0.002 USDC per call, x402, Base) and the fact that SPF and DMARC are returned parsed rather than raw. It does not describe error behavior or partial results.

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?

Two compact sentences, front-loaded with what the tool returns and followed by the price. Nothing is redundant or padded.

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 single-parameter lookup with full schema coverage, this covers what the tool does, what it returns, and what it costs. Only minor gaps remain, such as behavior for nonexistent domains or whether all record types are always emitted.

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?

Only one parameter exists and schema description coverage is 100%, including an example, so the schema does the semantic work. The description's 'of a domain' adds nothing beyond it, which is the expected baseline.

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 ('DNS records of a domain') and enumerates the exact record types plus parsed SPF/DMARC, so the agent knows precisely what it gets. It does not name or distinguish itself from any sibling, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no exclusions, and no mention of alternatives. The agent can only infer that this is the tool for resolving a domain's DNS, with nothing said about cases where a sibling lookup might be preferable.

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