Ripe Stat

Asn Neighbours

asn_neighbours

Read-onlyIdempotent

"BGP peers / neighbours of AS[N]" / "who does [ASN] peer with" / "upstream providers for [AS]" — BGP neighbours of an AS observed by RIPE's RIS (Routing Information Service) route collectors. Use for transit / peering analysis, network topology mapping.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`asn`	Yes	AS number

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No	BGP neighbours observed via RIS route collectors
`status`	No	API response status

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "asn": "AS15169"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "BGP neighbours observed via RIS route collectors",
+      "type": "object"
+    },
+    "status": {
+      "description": "API response status",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already cover readOnly, openWorld, idempotent, and non-destructive behavior. Description adds the data source (RIPE RIS) and the observational nature, which provides modest additional context beyond annotations.

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?

Single sentence efficiently packs synonyms, data source, and use cases. No redundancy or fluff.

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 tool with rich annotations and an output schema, the description provides sufficient context about data source and application, making it complete for correct invocation.

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?

With 100% schema description coverage, baseline is 3. Description reinforces the parameter's role but adds no extra format or syntax details beyond 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?

Description clearly states the tool returns BGP neighbours of an AS using RIPE RIS data, with specific synonyms and use cases for transit/peering analysis. Distinguishes itself from sibling tools like as_overview and bgp_state by focusing on neighbour relationships.

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?

Explanation of 'transit / peering analysis, network topology mapping' provides usage context. Does not explicitly contrast with siblings, but the domain-specific language helps agents select appropriately.

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.