Skip to main content
Glama
Sign In
mcp-ip2whois

mcp-ip2whois

Official
by ip2whois
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_hosted_domains

Look up all domain names hosted on a specified IP address (IPv4 or IPv6) and get the total count.

Instructions

Lookup for the list of hosted domain names by IP address.

Args:
    ip: The ip address (IPv4 or IPv6) to look up.

Returns:
    A JSON string result includes the domains hosted on the ip address, and the 
    total number of hosted domains found.

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": {
      "ip": "<ip>"
    },
    "name": "get_hosted_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are present, so description carries full burden. It discloses that the tool returns a JSON string with domains and total count, but does not mention any limitations, rate limits, error handling, or data source freshness. For a simple lookup, this is adequate but not highly transparent.

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?

The description is short and includes structured Args/Returns sections. It is clear and to the point, though the Returns section could be more concise.

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 tool with one parameter and no nested objects, the description covers the essential behavior. The presence of an output schema (even if not detailed here) reduces the need to explain return values further.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description adds clear meaning to the single required parameter 'ip', specifying it expects an IPv4 or IPv6 address. This significantly helps an agent understand what to provide.

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 is a lookup for hosted domain names by IP address. The verb 'Lookup' and resource 'hosted domain names' are specific, and it distinguishes from sibling tool 'get_whois' which does WHOIS lookups.

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?

The description implies usage context (reverse DNS lookups) but does not explicitly state when to use this tool versus alternatives. No exclusions or when-not-to-use guidance is provided.

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