Skip to main content
Glama

BRAINIAC Telecom & Network Infrastructure Intelligence

Analyze BGP route changes

network-intelligence_bgp-route-change-analyze

Compare before/after BGP route rows for AS-path, next-hop, and origin changes from caller-supplied tables. Price $0.04 USDC. POST /api/v1/network-intelligence/bgp-route-change-analyze. Unpaid calls return 402 and do not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "network-intelligence_bgp-route-change-analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
fileNo
jsonNo
logsNo
textNo
filesNo
configsNo
bgpRoutesNo
incidentsNo
publicDnsNo
publicTlsNo
dnsRecordsNo
reputationsNo
certificatesNo
latencySamplesNo
latencyAnomalyZNo
expiryWarningDaysNo
packetLossSamplesNo
packetLossWarnPctNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose valuable operational facts — $0.04 USDC cost, the POST endpoint, and that unpaid calls return 402 without running — which go beyond what the schema says. However, it says nothing about which parameter carries the before/after rows, how sides are paired, or how large a comparison is accepted.

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?

Three short sentences, front-loaded with the purpose; the pricing and HTTP details are compact and clearly separated. No filler, though the payment/endpoint sentences occupy space that could have gone to input guidance.

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?

Placeholder.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 20 parameters, so the description must compensate and does not. It never mentions the bgpRoutes array, the side enum (before/after/left/right/a/b) that determines pairing, or the alternative input channels (csv, json, text, file, files) — an agent cannot tell from the description how to supply the rows.

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 verb and resource ("Compare before/after BGP route rows") plus the exact attributes compared (AS-path, next-hop, origin), which is enough to distinguish it from nearby siblings like configuration-diff or dns-resolution-diagnose. It does not name an alternative explicitly, so it falls short of the top band.

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

Usage Guidelines3/5

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

"from caller-supplied tables" implies the agent must already have BGP route data to feed in, which is a useful usage constraint. But there is no explicit when-to-use versus configuration-diff, no statement about what inputs are mandatory (required parameters = 0), and no exclusion conditions.

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.

Resources