Skip to main content
Glama

x420_verify_domain-txt

Verify domain control by checking whether a DNS TXT record on the domain or a named subdomain exactly matches an expected token or key=token, proving zone control at query time.

Instructions

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. PAID: $0.02 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Returns: JSON: verified, matched_record, records_checked, checked_at - the deliverable plus X420's signed receipt and the settlement transaction. Example input: {"domain":"example.com","name":"_x420.example.com","token":"x420-8f3a7c1d"}.

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 observedv1.0.2

TDQS

A4/5.0
Behavior4/5

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

Annotations are sparse, and the description fills the gap well: live-DNS source, the exact price ($0.02 USDC per call), the Base/x402 settlement path, the wallet env var required, and the fact that real money moves. It also lists the response fields and notes the signed receipt and settlement transaction are included. It stops short of failure semantics (e.g. behavior when the record is absent or the payment fails).

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 is front-loaded in the first sentence, and payment/auth/return details are packed into a compact block with an example input. The professional-advice disclaimer sentence is boilerplate that does not help an agent select or invoke the tool, costing some conciseness.

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 compensates by enumerating the returned JSON fields and noting the receipt and settlement transaction. Combined with price, auth requirement, source of truth, and an example call, an agent has everything needed to invoke this tool correctly.

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?

Schema coverage is 100%, so the baseline is 3, and the description largely echoes the schema's own parameter descriptions plus an example. Its one genuine addition is the matching rule ('exactly or as key=token'), which clarifies what 'token' means at comparison time, but it does not explain the name-versus-domain relationship beyond the example.

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 ('Checks whether a domain ... publishes an expected token in DNS TXT') plus the matching modes ('exactly or as key=token'). It also bounds the claim ('Proves zone control at query time, nothing more'), which separates it from a generic DNS lookup even without naming a sibling.

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?

The scope line 'Proves zone control at query time, nothing more' tells the agent what this tool does not establish, which implicitly steers generic record fetches elsewhere. However, no sibling is named explicitly (e.g. x420_dns_lookup) and there is no explicit statement of when to prefer this over a plain DNS query.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.