Skip to main content
Glama

Whoisxml Whois History

whoisxml_whois_history
Read-onlyIdempotent

Historical WHOIS records for , past registrars, registrants, and creation/expiry dates over time. Example: whoisxml_whois_history({ 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_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name to look up historical WHOIS for, e.g. "google.com"
_apiKeyYesWhoisXML API key

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 profile is fully covered structurally. The description adds value by naming the kinds of records returned (past registrars, registrants, dates), but says nothing about historical depth, rate limits, API key requirements, or what happens on a domain with no history.

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?

Two short sentences, front-loaded with the resource and its returned fields. Nothing is padded, though the inline example largely duplicates the schema's examples array.

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 two-parameter read-only lookup with full schema coverage, complete annotations, and no output schema, the description covers what the tool does and what it returns. The remaining gap is missing guidance on choosing it over the sibling current-WHOIS tool, which is a routing rather than a completeness defect.

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%, so both the domain and _apiKey parameters are already documented in the schema. The description only restates the domain concept and repeats an example identical to the schema's examples entry, adding no new semantics such as domain format constraints or key sourcing.

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?

States a specific verb+resource combination: historical WHOIS records for a domain, and enumerates the returned facets (past registrars, registrants, creation/expiry dates). The word 'historical' implicitly separates it from the sibling whoisxml_whois, though it never names that sibling explicitly.

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 only implied by the adjective 'historical' and the phrase 'over time' – an agent can infer this is for tracking registration changes rather than current ownership. There is no explicit when-to-use statement, no exclusion, and no pointer to whoisxml_whois or whoisxml_reverse_whois as alternatives.

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.