Skip to main content
Glama

RDAP WHOIS Registration Info

whois
Read-onlyIdempotent

Return WHOIS/RDAP registration data for a domain: registrar, dates, status, and nameservers.

Related: dns.

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

Input Schema

NameRequiredDescriptionDefault
domainYesBare domain name such as example.com. No protocol (https://), path, or port; internationalized names in punycode (xn--...).

Output Schema

NameRequiredDescriptionDefault
domainNo
statusNoDomain status codes
createdNoRegistration creation date
expiresNoExpiration date
updatedNoLast updated date
registeredNoWhether the domain is currently registered
nameserversNoConfigured nameservers
registrar_nameNoRegistrar name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / required
      Removed value: -[
      -  "domain",
      -  "registered"
      -]
  2. Changed1 schema field changed
    • changedInput schema / properties / domain / description
      Previous value: -"Domain name"New value: +"Bare domain name such as example.com. No protocol (https://), path, or port; internationalized names in punycode (xn--...)."
  3. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered structurally. The description adds only that this is live registry data, with no mention of rate limiting, lookup latency, or what happens for unregistered or unsupported domains.

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?

The return-value summary is front-loaded and every listed field is informative. The closing 'Related: dns.' line is compact to the point of being cryptic, but it does not pad the text.

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?

For a one-parameter lookup with a fully described schema, complete annotations, and a declared output schema, the description covers purpose and payload adequately. The only real gap is the missing guidance on when to reach for this versus dns or registrar.

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 itself spells out the bare-domain requirement, punycode handling, and the prohibition on protocol/path/port. The description adds nothing beyond that, so the baseline of 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 gives a specific verb and resource ('Return WHOIS/RDAP registration data for a domain') and enumerates the payload (registrar, dates, status, nameservers), so the agent knows exactly what it gets. Sibling differentiation is attempted only via the terse 'Related: dns', which does not explain the boundary between the two.

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 or when-not-to-use guidance; the single word 'Related: dns' names a neighbor without stating the condition that selects one over the other. An agent must infer from the sibling names alone whether to call whois or dns first.

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.