Skip to main content
Glama

Ripe Stat Whois

ripe_stat_whois
Read-onlyIdempotent

"Whois lookup for IP / ASN / prefix" / "who owns IP [X]" / "WHOIS for [resource]", aggregated whois data for an IP address, IP prefix, or AS number across all five RIRs (ARIN, RIPE, APNIC, LACNIC, AFRINIC). Returns registrant org, registration country, abuse contacts, allocation date. Use for IP ownership, abuse-response, network forensics.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "resource": "8.8.8.8"
    },
    "name": "ripe_stat_whois"
  }
}

Input Schema

NameRequiredDescriptionDefault
resourceYesIP address, prefix, or AS number (e.g. "8.8.8.8", "8.8.8.0/24", "AS15169")

Output Schema

NameRequiredDescriptionDefault
dataNoWhois data aggregated across RIRs
statusNoAPI response status

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds the genuinely useful behavioral fact that a single call fans out to five RIRs, but it says nothing about coverage gaps, rate limits, or what happens with ambiguous or unallocated resources. With an output schema present, the return-field listing carries little extra weight.

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?

Effectively two compact sentences with the trigger phrasing front-loaded and the return fields listed after. The three quoted trigger phrases are somewhat boilerplate and duplicate the later content, but the overall size is well matched to a one-parameter lookup tool.

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?

Given a single required parameter, full schema coverage, an output schema, and rich annotations, the description covers what the tool does, what input forms it accepts, and the RIR aggregation behavior. The only shortfall is the missing contrast with overlapping siblings, which matters in a catalog this dense.

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 description coverage is 100% for the single resource parameter and the schema itself supplies examples for IP, prefix, and AS number forms. The description restates those same accepted input types without adding syntax or edge-case meaning beyond the schema, so baseline 3 applies.

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 names a specific verb (whois lookup) and resource set (IP address, IP prefix, AS number), and adds the meaningful scope detail that results are aggregated across all five RIRs. It is clear what the tool does, but it never distinguishes itself from plausible siblings like abuse_contact, network_info, or as_overview, which is the main clarity gap.

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?

'Use for IP ownership, abuse-response, network forensics' gives implied when-to-use contexts, so guidance is not absent. However, there is no when-not guidance and no named alternative, even though abuse_contact and network_info sit in the same catalog and would overlap on abuse-response and general network queries.

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.