Skip to main content
Glama

Domain registration facts (RDAP whois)

domain_whois
Read-only

Registration facts for a domain from its registry's RDAP server, located through the IANA bootstrap file: registrar name, IANA ID and abuse contact, created, updated and expiry dates, age and days to expiry, EPP status codes, transfer lock, nameservers, DNSSEC delegation flag, and the registry RDAP URL and terms link. No registrant contact data. Registries whose terms bar reuse (Nominet, CentralNic, Google Registry) are not queried. Price: $0.003 per successful call, paid in USDC with x402 v2; failed calls and calls that match nothing are not charged.

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

Input Schema

NameRequiredDescriptionDefault
domainYesBare domain, hostname, email address or URL. Scheme, path, port and credentials are stripped and IDNs are converted to punycode. IP addresses and private names are rejected. Facts describe the registrable domain (eTLD+1).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, it discloses unusual and decision-relevant behavior: coverage gaps for Nominet, CentralNic and Google Registry due to terms, absence of registrant data, and a per-call price of $0.003 in USDC via x402 v2 with failures and empty matches uncharged. That pricing and exclusion detail is not available in any structured field and directly affects whether an agent should call it.

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?

Front-loaded with purpose and source, then the field inventory, then the exclusion and billing caveats in priority order. The field enumeration is long but each item tells the agent what data is retrievable, so it earns its place; only minor trimming is possible.

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 one parameter and no output schema, the description carries the full burden of describing return values and does so exhaustively, plus cost and coverage limits. An agent has everything needed to decide, call, and interpret the result.

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% and the schema already documents normalization (scheme/path/port stripping, punycode, IP and private-name rejection). The description adds no additional parameter guidance, so the baseline 3 applies.

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 (registration facts for a domain) and names the data source mechanism (registry RDAP via IANA bootstrap). It then enumerates the exact returned fields, so an agent can tell this apart from DNS or email-auth siblings without opening 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the field list signals 'use this for registrar/expiry/nameserver ownership facts,' and it explicitly bounds coverage with 'No registrant contact data' and the list of non-queried registries. However, no sibling alternative is named for adjacent needs, so an agent must infer when domain_dns or domain_report is the better pick.

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