Skip to main content
Glama

Domain registration data via RDAP (modern WHOIS)

domain_whois
Read-only

Domain registration data via RDAP (modern WHOIS): registrar, creation, update and expiry dates, domain age in days, status flags and nameservers. Useful for trust and fraud checks. Takes 1-4 s. Free: 20 calls/day per user across free tools, no payment needed. Above that: $0.003 per call (x402, USDC on Base).

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": {
      "url": "<url>"
    },
    "name": "domain_whois"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses latency (1-4 s), a concrete rate limit (20 calls/day per user across free tools), and paid overflow pricing. Those operational facts materially change how an agent should batch or budget calls and are not available anywhere in the structured fields.

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?

Four short sentences, front-loaded with what the tool returns before the commercial terms, with no filler. The pricing/rate-limit sentences are dense but each carries a distinct operational fact.

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?

With no output schema, the description correctly takes on the job of enumerating returned fields, and it covers cost and latency for a metered external lookup. It stops short of saying what happens for unregistered or invalid domains, which is the main remaining ambiguity for an agent interpreting a 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%, so both the url and payment parameters are already fully documented in the schema. The description's pricing sentence corroborates the payment parameter's purpose but adds no syntax or format detail beyond it, so the baseline 3 applies.

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 description names a specific verb and resource ('Domain registration data via RDAP') and enumerates exactly what comes back: registrar, creation/update/expiry dates, domain age, status flags, nameservers. That is far more precise than a tautology. It does not explicitly contrast itself with near-neighbors like dns or https_check, which keeps it just short of a 5.

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?

'Useful for trust and fraud checks' gives an implied use case, so an agent knows the general context in which to reach for it. There is no explicit when-not guidance and no named alternative for cases like DNS resolution or TLS inspection, so the routing decision is only partially supported.

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.