Skip to main content
Glama

rdap_ip

Read-onlyIdempotent

Look up IP address registration data via RDAP to identify network ownership and allocation details.

Instructions

Look up IP address registration data via RDAP.

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

Input Schema

NameRequiredDescriptionDefault
ipYesIP address to look up.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is fully covered. 'via RDAP' adds a useful hint that results come from registry RDAP servers (authoritative, public, possibly rate-limited, possibly 404 for unregistered IPs), but the description never states rate limits, not-found behavior, or response shape.

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?

A single twelve-word sentence with the action and the target front-loaded and zero filler; nothing could be trimmed without losing meaning.

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 one-parameter, read-only lookup with a fully documented schema, complete annotations, and no output schema, the description carries enough to invoke the tool correctly. The only real gap is disambiguation from sibling IP-lookup tools and any note on failure modes for unregistered addresses.

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 100% and the single parameter is documented as 'IP address to look up.' The description adds nothing about accepted formats (IPv4 vs IPv6, CIDR acceptance), so it neither compensates for nor extends the schema.

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?

Specific verb ('Look up') plus a well-defined resource ('IP address registration data via RDAP'), which signals registry/WHOIS-style ownership data rather than geolocation. It does not, however, distinguish itself from the many IP-oriented siblings (ipinfo_lookup, ip_lookup, country_by_ip, bgpview_ip) beyond naming the RDAP protocol.

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 explicit when-to-use, when-not-to-use, or named alternative. An agent must already know what RDAP is and infer that this is the right tool when authoritative registration/ownership data is wanted instead of the geo/ASN lookups offered by siblings.

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