Skip to main content
Glama

X420 agent services

x420_domain_rdap

Read-onlyIdempotent

Domain registration (RDAP): Registration, expiry and last-changed dates, status flags, nameservers, registrar and DNSSEC for a domain from the registry's RDAP service (IANA bootstrap via rdap.org, free, no key). Source: registry RDAP. Not professional, legal, insurance, engineering, medical, financial or tax advice. Price: $0.03 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: registered, registration_date, expiration_date, days_to_expiry, status[], nameservers[], registrar, dnssec, source.

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

Input Schema

NameRequiredDescriptionDefault
domainYesdomain name, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already establish readOnly/idempotent/non-destructive/openWorld, and the description goes well beyond them: it discloses pricing ($0.03 USDC on Base), the critical caveat that this hosted tool does NOT return the deliverable, and the exact x402 payment mechanics. It also previews the paid JSON payload, which an agent needs to decide whether the call is worth funding.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and payment model are front-loaded, which is good, but the text is bloated by the long professional/legal/insurance/medical disclaimer and by redundant restatements of the RDAP source ('Domain registration (RDAP)', 'registry's RDAP service', 'Source: registry RDAP'). The essential payment-instruction content is valuable; the boilerplate is not.

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 proxy tool with no output schema, the definition covers everything an agent needs: what data is returned, the deliverable field list, the price and payment protocol, and the local-server alternative. Nothing material about invocation or expectation-setting is missing.

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?

The single parameter is fully documented in the schema ('domain name, e.g. example.com'), so the schema already carries the semantics. The description adds nothing about accepted input forms (apex vs. subdomain, IDN, TLD scope), so it neither compensates nor adds value here.

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?

The first sentence names a specific verb+resource (domain registration/RDAP) and enumerates the returned fields: registration, expiry, last-changed dates, status flags, nameservers, registrar, DNSSEC. It is clearly distinct from a generic DNS or TXT-verification tool in substance, though it never names a sibling (e.g. x420_dns_lookup) to make the distinction explicit.

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?

Operational usage is well covered: it states the hosted tool validates input and returns payment instructions, gives the exact 402/PAYMENT-SIGNATURE retry loop, and offers the local x420-mcp server as an alternative path. However, there is no guidance on when to choose this registry-RDAP call over sibling lookups such as x420_dns_lookup or x420_verify_domain-txt, so selection guidance against alternatives is implied rather than stated.

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