Skip to main content
Glama

Ripestat Announced Prefixes

ripestat_announced_prefixes
Read-onlyIdempotent

"What IP ranges does AS[N] announce" / "all prefixes for [ASN]" / "what IP blocks does Cloudflare / Google / AWS own" / "netblocks announced by [AS]", every IPv4 and IPv6 prefix currently announced in global BGP by an Autonomous System, as seen by RIPE's RIS route collectors. AUTHORITATIVE for "which IP ranges belong to this network": use it to build allowlists, attribute traffic to a provider, or size a network's address footprint. Note RIPEstat excludes prefixes seen by fewer than 10 full-feed peers, so very low-visibility announcements are omitted.

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": {
      "asn": "AS13335"
    },
    "name": "ripestat_announced_prefixes"
  }
}

Input Schema

NameRequiredDescriptionDefault
asnYesAS number (e.g. "AS13335" or "13335")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/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 covered. The description adds genuinely new behavioral context: the data source (RIPE RIS route collectors) and the important caveat that prefixes seen by fewer than 10 full-feed peers are excluded, which affects completeness of results.

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?

Front-loads the core question and answer in the first clause, then layers authority, use cases, and the visibility caveat. The quoted query phrasings are dense but each maps to a real user intent, and no sentence is wasted.

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 single-parameter read tool with no output schema, the description covers what is returned (all IPv4 and IPv6 prefixes), the source, and the known limitation on low-visibility announcements. Nothing an agent needs to call it correctly is missing.

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 'asn' parameter is documented with format examples in the schema itself. The description reinforces the AS[N] notation but adds no syntax or format detail beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb and resource ('every IPv4 and IPv6 prefix currently announced in global BGP by an Autonomous System') and frames it with concrete query phrasings. It is clearly distinguishable from siblings like asn_search, as_overview, or bgp_state, which do not return the full announced-prefix set.

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?

Gives explicit use cases — building allowlists, attributing traffic to a provider, sizing address footprint — and asserts authority for 'which IP ranges belong to this network'. It does not name a sibling alternative or state when not to use it, so it stops short of a 5.

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.