Skip to main content
Glama

domain_whois

Retrieve domain registration data via RDAP to check registrar, key dates, status, nameservers, DNSSEC, and public contacts without an API key.

Instructions

Registration data for a domain via RDAP (the modern WHOIS replacement).

Returns registrar, creation/expiry/update dates, status flags, nameservers, DNSSEC state and public contacts. No API key needed.

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
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does disclose useful behavior: the protocol used, the fields returned, and that no API key is required. It omits failure behavior (nonexistent domains, TLDs unsupported by RDAP) and any rate-limit or latency expectations for an external network lookup.

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?

Three short sentences, front-loaded with the core purpose and the RDAP clarification, followed by the return fields and the auth note. No filler, though the field list is a run-on that could be tightened.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with no output schema, enumerating the returned fields is the right compensation and it is done adequately. The gap is the domain-parameter format and error cases, which matter for an external RDAP call against arbitrary domain strings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required 'domain' parameter, and the description adds nothing about its expected form — registrable apex domain, subdomain, IDN, or trailing-dot handling are all unstated. The low coverage means the description should compensate, and it does not.

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 resource (domain registration data) and the mechanism (RDAP, the modern WHOIS replacement), so an agent knows exactly what it fetches. It does not explicitly contrast with sibling lookups like ip_whois or otx_domain, so sibling differentiation rests on the name alone.

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 at all — nothing tells the agent to prefer this over ip_whois for IPs or otx_domain/recon_domain for domain intel. The only contextual note is 'No API key needed,' which is a prerequisite, not usage guidance.

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