Skip to main content
Glama

Agent Exchange store

verify_dns

$0.002 via x402: A single DNS lookup over DNS-over-HTTPS (Cloudflare 1.1.1.1): any record type (A, AAAA, MX, TXT, NS, CNAME, SOA, SRV, CAA, PTR), with TTLs and the DNSSEC AD flag. Pay 0.002 USDC through https://store.agentexchange.work/gw/verify/dns?name=example.com&type=TXT Via the Agent Exchange store gateway; settled by Coinbase.

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

Input Schema

NameRequiredDescriptionDefault
nameYesname
typeNorecord type, default A
x_paymentNoSigned x402 payment payload (optional; without it the answer is the price)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses the cost ($0.002 USDC), the x402 payment mechanism, the gateway URL, that it settles via Coinbase, and that without a payment payload the answer is the price. It also notes TTL and DNSSEC AD flag inclusion. Remaining gaps are error/rate-limit behavior.

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?

Dense but front-loads the key fact (cost) and then the substantive behavior. The embedded gateway URL is somewhat noisy, but every clause conveys actionable information rather than filler.

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?

No output schema exists, and the description compensates by stating what the return contains (records, TTLs, DNSSEC AD flag). Combined with the payment flow explanation, an agent has enough to invoke and interpret it, though error/edge-case behavior is unstated.

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, but the description adds real value: it enumerates the valid record types (A, AAAA, MX, TXT, NS, CNAME, SOA, SRV, CAA, PTR) beyond the schema's terse 'record type, default A', and its example URL clarifies how name and type map into the request.

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 ('A single DNS lookup over DNS-over-HTTPS (Cloudflare 1.1.1.1)') and enumerates the record types it supports, which cleanly separates it from siblings like verify_domain and verify_email. An agent can identify exactly what this returns (DNS records with TTLs and the DNSSEC AD flag).

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?

Implied usage is clear from the name and purpose (look up a DNS record), and the payment workflow is spelled out. However, there is no explicit guidance on when to choose this over verify_domain or other verification siblings, and no statements about rate limits or failure conditions.

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