Skip to main content
Glama

IP address registration

ip_whois
Read-only

Who holds an IP address block, from the Regional Internet Registry: the block, holder, country, abuse contact and dates. Needs a DomainDrift API key.

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": "ip_whois"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipYesAn IPv4 or IPv6 address, e.g. "1.1.1.1"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds genuinely new context: the authoritative source (RIR), the fields that come back, and the API-key requirement. It stops short of noting coverage caveats, rate limits, or behavior for unallocated addresses.

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 sentences, zero filler, front-loaded with the question answered and the returned fields, with the auth prerequisite placed last. Every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with no output schema, listing the response fields (block, holder, country, abuse contact, dates) fills the gap an absent output schema would leave. An agent has everything needed to decide and call correctly.

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?

The single 'ip' parameter is fully documented in the schema with an example ("1.1.1.1"), so the description need not repeat it. It adds no meaning beyond the schema, which is the expected baseline at 100% coverage.

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?

States a specific question the tool answers ('Who holds an IP address block') plus the source (Regional Internet Registry) and the exact fields returned. The framing around an IP block cleanly separates it from the domain-oriented siblings such as whois_lookup and lookup_domain.

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 by the resource (look up IP registration data), and a prerequisite is stated ('Needs a DomainDrift API key'), but there is no explicit when-to-use or when-not guidance and no routing to alternatives like asn_whois or whois_history.

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.

Resources