Skip to main content
Glama

whois_domain

Retrieve domain registration details including ownership, registration dates, and availability status through WHOIS lookups.

Instructions

Looksup whois information about the domain

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYes

Implementation Reference

  • src/index.ts:11-29 (registration)
    Registers the 'whois_domain' MCP tool with description, Zod input schema {domain: z.string().min(1)}, and an async handler that calls whoisDomain(domain) from 'whoiser' package, formats the result as text content or error.
    server.tool(
      'whois_domain',
      'Looksup whois information about the domain',
      { domain: z.string().min(1) },
      async ({ domain }) => {
        try {
          const result = await whoisDomain(domain);
          return {
            content: [{ type: 'text', text: `Domain whois lookup for: \n${JSON.stringify(result)}` }],
          };
        } catch (err: unknown) {
          const error = err as Error;
          return {
            content: [{ type: 'text', text: `Error: ${error.message}` }],
            isError: true
          };
        }
      }
    );
  • The handler function for the whois_domain tool. It performs a WHOIS lookup using the external whoisDomain function and returns the result as structured text content or an error response.
    async ({ domain }) => {
      try {
        const result = await whoisDomain(domain);
        return {
          content: [{ type: 'text', text: `Domain whois lookup for: \n${JSON.stringify(result)}` }],
        };
      } catch (err: unknown) {
        const error = err as Error;
        return {
          content: [{ type: 'text', text: `Error: ${error.message}` }],
          isError: true
        };
      }
    }
  • Input schema for the whois_domain tool using Zod: requires a non-empty string 'domain'.
    { domain: z.string().min(1) },
Behavior2/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 states the action ('looksup whois information') but doesn't disclose behavioral traits like rate limits, authentication needs, error conditions, or what specific whois information is returned. For a tool with zero annotation coverage, this is inadequate.

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?

Extremely concise - a single sentence with zero waste. Front-loaded with the core action. Every word earns its place, though this conciseness contributes to gaps in other dimensions.

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

Completeness2/5

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

Given zero annotation coverage, no output schema, and low schema description coverage, the description is incomplete. It states the basic purpose but lacks crucial context about behavior, parameters, and results needed for effective tool use. For a whois lookup tool, more detail about return values and constraints would be expected.

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%, so the description must compensate. It mentions 'domain' but provides no semantic context beyond what's in the schema (a required string). No details on domain format (e.g., TLD requirements, validation), examples, or constraints are given. The description adds minimal value over the bare schema.

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 clearly states the tool's purpose: 'Looksup whois information about the domain' - a specific verb ('looksup') and resource ('whois information about the domain'). It doesn't explicitly differentiate from siblings (whois_as, whois_ip, whois_tld), but the domain focus is implied. Not tautological with the name 'whois_domain'.

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?

No guidance on when to use this tool versus alternatives. The description doesn't mention sibling tools or provide context for choosing domain lookups over AS, IP, or TLD lookups. Usage is implied by the domain parameter but not explicitly stated.

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/modelcontextprotocol-servers/whois-mcp'

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