Skip to main content
Glama

ip_whois

Retrieve RDAP registration details for an IP address, including network range, holder, ASN, contacts, and events, to identify ownership and network context.

Instructions

RDAP registration data for an IP: network range, holder, ASN, contacts, events.

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
ipYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. 'Registration data' implies a read-only lookup, but it does not state that this queries an external RDAP service, whether auth or rate limits apply, how unregistered or private IPs are handled, or whether results are cached — all material for an agent planning a call.

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?

A single compact sentence with the resource scope front-loaded and the return payload enumerated. No filler, though the fragment style leaves no room for usage or behavioral cues.

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

Completeness3/5

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

For a one-parameter lookup with no output schema, the description adequately conveys what comes back. It falls short on annotation-free behavior (service dependency, failure modes) and on distinguishing this from closely related IP/ASN siblings.

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 coverage is 0% and the single parameter 'ip' has only a title, so the description must compensate. The phrase 'for an IP' does imply the parameter is the target IP address, which is reasonable for one obvious parameter, but no format details (IPv4/IPv6, CIDR handling) are added.

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 gives a specific verb+resource combination: RDAP registration lookup for an IP address, and enumerates the returned data (network range, holder, ASN, contacts, events). This distinguishes it at the resource level from domain_whois (domains), though it does not explicitly differentiate from overlapping siblings like ip_intel, recon_ip, or asn_lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance at all. Given siblings such as asn_lookup, ip_intel, and recon_ip that plausibly return overlapping IP/ASN data, an agent gets no signal about which to pick or in what order.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.