Skip to main content
Glama

x420_domain_rdap

Fetch a domain's RDAP registration details—registration and expiry dates, status flags, nameservers, registrar, and DNSSEC—to verify domain age, ownership status, and renewal deadlines.

Instructions

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. PAID: $0.03 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Returns: JSON: registered, registration_date, expiration_date, days_to_expiry, status[], nameservers[], registrar, dnssec, source - the deliverable plus X420's signed receipt and the settlement transaction. Example input: {"domain":"example.com"}.

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

TDQS

A3.5/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, so the non-read-only nature of a lookup tool would otherwise be puzzling; the description earns credit by explaining the cause: $0.03 USDC settled on Base via x402 from X420_MCP_WALLET_PRIVATE_KEY, real money. It also discloses that the response carries a signed receipt and settlement transaction, which is behavior beyond the annotations. It does not cover failure/refund behavior or repeat-call cost implications, so it stops short of full disclosure.

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, return fields, pricing/settlement, and an example are front-loaded in one dense paragraph with no wasted sentences. The generic 'not professional, legal, insurance, engineering, medical, financial or tax advice' disclaimer is boilerplate that does not help an agent decide or invoke.

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, but the description enumerates the returned JSON keys explicitly plus the receipt and settlement transaction, which is what an agent needs to plan downstream steps. Payment mechanics and the required wallet env var are covered; error/empty-result behavior is the main remaining gap.

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 description coverage is 100% for the single domain parameter, so the schema already carries the meaning and the baseline of 3 applies. The description adds only a matching example input ({"domain":"example.com"}), with no input-normalization or format caveats beyond the schema.

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+resource (domain registration via RDAP) and enumerates exactly what is returned: registration/expiry/last-changed dates, status flags, nameservers, registrar, DNSSEC. The named data source (registry RDAP, IANA bootstrap via rdap.org) also separates it in an agent's mind from DNS-lookup style siblings without needing to open a schema.

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 when-to-use / when-not-to-use guidance and no alternative is named; nothing tells an agent to prefer this over x420_dns_lookup or x420_verify_domain-txt when registration metadata happens to be what they need. The enumerated return fields imply the use case, but that is inference rather than instruction.

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