Skip to main content
Glama

Whoisxml Whois

whoisxml_whois
Read-onlyIdempotent

Current WHOIS for , registrar, creation/expiry dates, registrant org, name servers, and status. Example: whoisxml_whois({ domain: "google.com", _apiKey: "your-key" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "google.com",
      "_apiKey": "your-whoisxml-api-key"
    },
    "name": "whoisxml_whois"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name to look up, e.g. "google.com" (no protocol)
_apiKeyYesWhoisXML API key (get one at whoisxmlapi.com, one key works across all products)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"WhoisXML API key (get one at whoisxmlapi.com — one key works across all products)"New value: +"WhoisXML API key (get one at whoisxmlapi.com, one key works across all products)"
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety and idempotency profile is covered. The description adds value by listing the data fields a caller will receive, which is the main behavioral unknown with no output schema, but it says nothing about quota, rate limits, or what happens for an unregistered/invalid domain.

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?

Two sentences, front-loaded with the purpose and then the payload fields. The example call is largely redundant with the schema's examples array, which is the only real waste.

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 simple two-parameter read tool with rich annotations, the description covers identity and expected return fields, which is most of what an agent needs. Missing only edge-case behavior (invalid domain, rate limiting) and API key scope, which the schema partially handles.

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 description coverage is 100%, including the 'no protocol' constraint on domain and how to obtain the API key, so the schema already carries parameter meaning. The inline example in the description merely restates what the schema's examples array already shows, adding nothing new.

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 the resource (WHOIS for <domain>) and enumerates the returned fields — registrar, creation/expiry dates, registrant org, name servers, status. The word "Current" hints at a contrast with whoisxml_whois_history, but the sibling is never named, so differentiation is only implied.

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?

There is no explicit when-to-use or when-not-to-use guidance and no alternative is named. A reader can infer that this is the live-lookup tool as opposed to the history variant, but that inference rests entirely on the word "Current".

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.