Skip to main content
Glama

Bgp State

bgp_state
Read-onlyIdempotent

"BGP routes for [prefix]" / "what AS announces [IP]" / "BGP hijack check" / "current routing state for [resource]", origin ASNs and AS-path lengths currently announcing a resource on the global BGP table. Use to detect BGP hijacks, audit route propagation, find anycast announcers.

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.0/24"
    },
    "name": "bgp_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
resourceYesIP, prefix, or ASN

Output Schema

NameRequiredDescriptionDefault
dataNoCurrent BGP routing state with origin ASNs and path lengths
statusNoAPI response status

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "resource": "8.8.8.0/24"
      +  },
      +  {
      +    "resource": "AS15169"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "data": {
      +      "description": "Current BGP routing state with origin ASNs and path lengths",
      +      "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 readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that results reflect the global BGP table at query time ('currently announcing'), implying a live snapshot. It does not mention collector lag, coverage gaps, or what happens for unannounced/private ranges, which would matter for hijack conclusions.

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?

The query-phrase list is front-loaded to anchor intent and is followed by one clarifying clause on what is actually returned. It is slightly verbose in the quoted variants but no sentence is wasted.

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?

With an output schema present, return-value explanation is unnecessary, annotations cover safety, and there is only one well-documented parameter. What is missing is minor operational context such as data freshness or how IPv4 vs IPv6 and ASN inputs are normalized.

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?

There is a single parameter with 100% schema description coverage ('IP, prefix, or ASN'), plus schema examples for both a prefix and an ASN. The description's bracketed placeholders ([prefix], [IP], AS15169) reinforce accepted input forms but add no syntax detail beyond the schema, so the baseline of 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 the resource precisely: origin ASNs and AS-path lengths currently announcing a resource on the global BGP table, and the quoted phrasings ('BGP hijack check', 'what AS announces [IP]') make intent unambiguous. It does not distinguish itself from plausible siblings such as prefix_overview or as_overview, so it stops 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?

It gives concrete use cases: detect BGP hijacks, audit route propagation, find anycast announcers. That tells an agent when to reach for it, but there is no explicit when-not guidance or named alternative for adjacent routing/prefix tools.

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.