Skip to main content
Glama
duksh

PeerGlass

by duksh

rir_query_ip

Read-onlyIdempotent

Query all 5 global RIRs simultaneously for IP address registration details using RDAP. Returns normalized results with owner, country, allocation date, and abuse contact information.

Instructions

Query all 5 global RIRs simultaneously for an IP address using RDAP.

Fires parallel RDAP requests to AFRINIC, APNIC, ARIN, LACNIC, and RIPE NCC. Exactly one RIR will be authoritative; the others return 'not found'. Normalizes all responses into a unified schema and returns a clear summary.

Results are cached for 1 hour to respect RIR rate limits.

Args: params (IPQueryInput): - ip_address (str): IPv4 or IPv6 address e.g. '1.1.1.1', '2001:4860:4860::8888' - response_format (str): 'markdown' (default) or 'json'

Returns: str: Registration details including prefix, owner, country, allocation date, abuse email, and responses from all 5 RIRs. JSON schema: { "ip": str, "results": [{"rir": str, "status": str, "error": str|null}], "normalized": [{"rir": str, "prefix": str, "name": str, "org_name": str, "country": str, "allocation_date": str, "abuse_email": str}] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Excellent disclosure beyond the annotations: it reveals the parallel request pattern to all 5 RIRs (AFRINIC, APNIC, ARIN, LACNIC, RIPE NCC), the normalization of responses into a unified schema, and the 1-hour caching behavior for rate limit compliance. This provides crucial context for a distributed query operation.

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?

Well-structured with clear sections pivoted from general description to Args to Returns. The information is front-loaded with the core purpose in the first sentence. The JSON schema block in Returns is verbose but appropriately detailed for a complex return structure.

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?

Comprehensive coverage appropriate for a multi-API tool: includes input/output schemas, behavioral details (parallelism, normalization), performance constraints (caching, rate limits), and the complete JSON response structure. Nothing critical is missing given the output schema is present.

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 Args section documents parameters with examples (e.g., '1.1.1.1' and '2001:4860:4860::8888'), but largely duplicates the well-described input schema. It does add explicit mention of the default value ('markdown') for response_format, which complements the schema.

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 the tool 'Query[s] all 5 global RIRs simultaneously for an IP address using RDAP,' which is a specific verb-resource combination that distinguishes it from siblings like rir_query_asn or rir_get_abuse_contact.

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?

It explains that exactly one RIR will be authoritative while others return 'not found,' setting correct expectations for the parallel query pattern. It also documents the 1-hour cache to respect rate limits, providing operational context. It could explicitly mention when to use single-RIR alternatives, but the scope is clearly defined.

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/duksh/peerglass'

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