Skip to main content
Glama

x420_verify_domain-txt

Read-onlyIdempotent

Domain TXT challenge: Checks whether a domain (or a named subdomain of it) publishes an expected token in DNS TXT, exactly or as key=token. Source: live DNS. Proves zone control at query time, nothing more. Not professional, legal, insurance, engineering, medical, financial or tax advice. Price: $0.002 USDC per call (x402 on Base). This hosted tool does NOT pay and does NOT return the deliverable: it validates the input and returns payment instructions (pay_to, network, price and the x402 URL to pay at). GET the url; read PAYMENT-REQUIRED from the 402; retry with PAYMENT-SIGNATURE (x402 v2). Or run the local x420-mcp server with your own wallet key to pay automatically. Deliverable once paid: JSON: verified, matched_record, records_checked, checked_at.

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>",
      "token": "<token>"
    },
    "name": "x420_verify_domain-txt"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNorecord name to query (default: the domain itself), e.g. _x420.example.com
tokenYesexpected token value
domainYesdomain to verify, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already mark this read-only, idempotent, open-world and non-destructive, but the description adds behavior that annotations cannot express: this hosted tool does NOT pay and does NOT return the deliverable, instead returning payment instructions (pay_to, network, price, x402 URL). It also discloses price, the x402 protocol steps, and the exact deliverable shape once paid.

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?

Purpose and scope are front-loaded, then the essential payment mechanics, then the deliverable fields. The one sentence that does not carry operational information is the legal/advice disclaimer boilerplate, which is the only soft spot in an otherwise dense, well-ordered description.

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?

For a paid, gated tool with no output schema, it covers everything an agent needs: what is verified, what is proven, the payment handshake, the alternative local-wallet path, and the return field names. No material gap remains.

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 meaning: the domain may be a named subdomain, and the token may match either exactly or in key=token form. The schema alone does not convey those matching semantics.

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?

The opening sentence names a specific verb and resource ('Checks whether a domain ... publishes an expected token in DNS TXT') and states the two matching modes (exact or key=token), which distinguishes it from the general x420_dns_lookup sibling without needing to name it.

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?

It gives clear scope guidance ('Proves zone control at query time, nothing more') and describes the full invocation path for the hosted variant: GET the url, read PAYMENT-REQUIRED from the 402, retry with PAYMENT-SIGNATURE, or use the local server. It stops short of naming an alternative tool for plain DNS reads, so it is strong context rather than explicit when/when-not routing.

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