Skip to main content
Glama
Sign In
Cloady

Cloady

Official
by Cloady
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Get Whois

getWhois
Read-only

Retrieves a domain's RDAP registration details—registrar, dates, statuses, nameservers, DNSSEC, redacted registrant—to verify ownership and DNS setup, and checks nameservers when RDAP is unavailable.

Instructions

What the domain's registry publishes over RDAP: registrar, dates, statuses, nameservers, DNSSEC and the registrant, which is usually redacted. For an extension without RDAP, only whether the domain has nameservers is known. Public: no token 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": "getWhois"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.18.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish read-only, open-world, non-destructive behavior, and the description adds useful context: registrant data is usually redacted, RDAP availability varies by extension, and access is public without a token. It does not discuss rate limits or error behavior, but it substantially improves behavioral understanding.

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 three tight sentences, front-loaded with what the registry publishes, followed by the RDAP limitation and public-access note. Every sentence adds relevant information without repetition.

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 no output schema, the description explains what data may be returned, the redaction caveat, the fallback when RDAP is unavailable, and the authentication posture. The main gap is the lack of input-format guidance for the domain parameter.

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?

The single domain parameter has 0% schema description coverage, so the description must carry the burden of explaining expected input format. It mentions domains and extensions but does not clarify whether the input should be an apex domain, punycode, subdomain, or TLD-only value.

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 identifies the resource: domain registry data published over RDAP, including registrar, dates, statuses, nameservers, DNSSEC, and registrant. It is specific enough to distinguish a WHOIS/RDAP lookup from general DNS checks, though it does not explicitly name sibling alternatives.

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?

Usage is implied for retrieving registry information about a domain, and the description notes the no-RDAP fallback and that no token is needed. It does not explicitly say when to use this instead of checkDns, checkDomains, or listWorkspaceDomains.

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

Deploy Server

Other Tools