Skip to main content
Glama

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.

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": "AS15169"
    },
    "name": "asn_neighbours"
  }
}

Input Schema

NameRequiredDescriptionDefault
asnYesAS number

Output Schema

NameRequiredDescriptionDefault
dataNoBGP neighbours observed via RIS route collectors
statusNoAPI response status

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive behavior, so the safety profile is covered. The description adds genuine context by attributing the data to RIPE RIS route collectors, hinting at observation-based coverage rather than registry truth, but it does not state that results are vantage-point dependent or may be incomplete — a relevant caveat for BGP visibility data.

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?

Front-loads three natural-language query phrasings that aid intent matching, followed by the data source and use cases. The quoted alternatives are slightly redundant with each other but each is short and purposeful.

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?

For a single-parameter lookup with full schema coverage and an output schema, the description supplies purpose, source, and use cases — enough to call it correctly. The only meaningful omission is guidance on data-currency or vantage-point limitations of RIS-derived peering data.

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% with an example ('AS15169'), so the schema does most of the work. The description's use of 'AS[N]' / '[ASN]' hinting implies the AS-prefix input format, which is mildly additive but not articulated as a format rule.

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?

States a specific resource (BGP peers/neighbours of an AS) and names the underlying data source (RIPE RIS route collectors), which lets an agent understand exactly what is returned. It does not explicitly differentiate itself from overlapping siblings such as bgp_state or as_overview, so it falls short of a 5.

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?

Explicitly names the intended analyses ('transit / peering analysis, network topology mapping'), giving clear context for selection. It stops short of stating when-not to use it or pointing to the sibling tools that cover adjacent questions.

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.