Skip to main content
Glama

whois_lookup

Retrieve WHOIS registration data for a domain to check expiry, registrar, nameservers, and ownership details for domain due diligence.

Instructions

Retrieve WHOIS registration data for a domain name.

Returns publicly available registration details from WHOIS databases.
Useful for domain due diligence, checking expiry before purchasing,
identifying registrar, or investigating domain ownership.

Note: Many registrars apply GDPR redaction to registrant contact details.
Technical data (nameservers, dates, registrar) is always available.

Args:
    domain: Domain to look up (e.g. 'example.com'). Supports most TLDs.

Returns:
    registrar: Registrar name and IANA ID.
    registered_at: Domain creation date (ISO 8601).
    expires_at: Expiry date — domain may be purchased after this.
    updated_at: Last modification date.
    nameservers: List of authoritative nameservers.
    status: EPP status codes (e.g. clientTransferProhibited).
    registrant: Registrant contact (may be redacted under GDPR).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYes
Behavior5/5

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

No annotations are provided, so the description carries full burden. It discloses GDPR redaction effects on contact details and notes that technical data is always available, providing transparency beyond the basic action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is efficiently structured with an intro, a note, and clear Args/Returns sections. It is front-loaded with the main purpose and every sentence adds value without redundancy.

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?

Despite no output schema, the description details all expected return fields with types and notes. It covers limitations (GDPR), making it complete for a look-up tool of moderate complexity.

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

Parameters5/5

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

The single parameter 'domain' is described with format and example ('example.com') and TLD support, adding significant meaning beyond the schema's type definition. Coverage is 0% in schema, but description fully compensates.

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?

The description clearly states the tool retrieves WHOIS registration data for a domain name, using a specific verb and resource. It is distinct from sibling tools like dns_lookup or ip_lookup, with no ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description lists use cases such as domain due diligence, expiry checking, and registrar identification. While it does not explicitly state when not to use the tool or mention alternatives, the context is clear and actionable.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ForeverTools/kiprio-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server