Ripe Stat

Prefix Overview

prefix_overview

Read-onlyIdempotent

"Prefix overview for [CIDR]" / "info on IP block [X/Y]" — comprehensive summary for an IP prefix: BGP announcements, origin ASes, allocation history. Use to understand a whole IP block at once instead of chaining bgp_state + whois.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`resource`	Yes	Prefix (e.g. "8.8.8.0/24")

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No	Comprehensive prefix overview with announcements, origins, allocation
`status`	No	API response status

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "resource": "8.8.8.0/24"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Comprehensive prefix overview with announcements, origins, allocation",
+      "type": "object"
+    },
+    "status": {
+      "description": "API response status",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already indicate safe, read-only, idempotent behavior. The description adds valuable context about what the summary includes (BGP announcements, origin ASes, allocation history) beyond what annotations provide. No behavioral downsides are omitted.

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 concise lines with examples and purpose, no wasted words. Front-loaded with common query patterns.

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 simple one-parameter tool with an output schema, the description fully covers the tool's purpose, data returned, and usage guidance. No gaps.

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% for a single parameter with a clear description. The description reinforces the parameter meaning with example formats '[CIDR]' and '[X/Y]', adding slight value over the schema alone.

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 that the tool provides a comprehensive summary for an IP prefix including BGP announcements, origin ASes, and allocation history. It uses clear verb phrases like 'Prefix overview' and 'comprehensive summary'. It distinguishes itself from siblings by noting it replaces chaining bgp_state and whois.

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

Usage Guidelines5/5

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

Explicitly says 'Use to understand a whole IP block at once instead of chaining bgp_state + whois', providing clear when-to-use guidance and naming alternatives.

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

All Ripe Stat tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.