Skip to main content
Glama
ip2whois

mcp-ip2whois

Official
by ip2whois
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_whois

Retrieve domain registration details including expiry date, registrar name, and owner information. Use this to check domain ownership and nameservers.

Instructions

Lookup WHOIS data for a domain name. Use this tool when the user asks about 
domain registration details, registrar names, expiry dates, domain ownership, 
or nameservers for a specific website (e.g., 'google.com').

Args:
    domain: The domain name to look up (e.g., 'example.com').

Returns:
    A JSON string result includes domain age, update and expiry date, assiociated nameservers, registrar and registrant information, and admin, tech and billing information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.5/5.0
Behavior4/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 describes the return format and fields, indicating it is a read-only lookup, but does not mention error handling or authorization needs.

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 concise with an effective structure: purpose statement, Args, Returns. Every sentence adds value with no 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?

Given the tool is simple with one parameter and an output schema, the description covers parameter and return data well. It lacks mention of errors or limitations, but is otherwise complete.

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 domain parameter is clearly described with purpose and an example. Schema has no description (0% coverage), so the description fully compensates by explaining what the parameter is.

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 it performs a WHOIS lookup for a domain name, listing specific details like registrar, expiry, nameservers, etc. It is distinct from the sibling tool get_hosted_domains by focusing on registration data.

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?

Explicitly says when to use this tool: when user asks about domain registration details, registrar, expiry, etc. However, it does not mention when not to use or differentiate from the sibling tool.

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/ip2whois/mcp-ip2whois'

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