Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

by Jambozx
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

network_bgp_route_lookup

Retrieve live BGP routing data for an IPv4/IPv6 address or CIDR prefix: origin AS, AS-PATH, and alternative paths.

Instructions

BGP Route Lookup. Resolve an IPv4/IPv6 address or CIDR prefix to live BGP routing data: origin AS, AS-PATH, announced prefix, upstream/alternative paths, and path analysis. Makes a live outbound network call to a public BGP looking-glass API (BGPView), so results depend on third-party availability and may vary between calls. Use this when you need the routing path / AS-PATH for an address; use network_asn_lookup for plain AS number and network ownership, network_whois for registry/registration records, and network_ip_geolocation for physical location. Read-only and non-destructive, but not idempotent (reflects current global routing state). Anonymous callers are limited to 10 requests/minute, 60/hour, 200/day; CAPTCHA is required above 30 requests/hour. Returns primaryRoute (asPath, origin, asNames), alternativePaths, routeCount, pathAnalysis, and the routeServer used.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesIPv4/IPv6 address or CIDR prefix to look up (e.g. 8.8.8.8 or 8.8.8.0/24). Required; validated as an IP or CIDR before any query.
routeServerNoRouting data source. Only bgpview is implemented; route-views and ripe-ris fall back to BGPView.bgpview
showAlternativePathsNoInclude up to three upstream/alternative AS paths in the result.
showRouteAttributesNoInclude path-analysis attributes (hop count, geographic path, diversity).
resolveASNNamesNoResolve AS numbers to organisation names in the asNames map.
showPathLatencyNoInclude estimated path-latency analysis (best-effort; latency is not measured).
worker_idNoOptional registered healthy worker peer ID. Omit to use the default master-server behavior.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
primaryRouteNoBest-matching route, or null if no route was found.
alternativePathsNoUp to three upstream AS paths (when showAlternativePaths is true).
routeCountNoTotal routes found (primary plus alternatives).
pathAnalysisNoPath metrics (present when showRouteAttributes or showPathLatency is true).
routeServerNoRouting data source actually used.
errorNoPresent only on failure (400/500): describes the error.

Tool Definition Quality

A4.6/5.0
Behavior5/5

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

Annotations are minimal (readOnlyHint: false, destructiveHint: false). The description adds substantial behavioral context: read-only, non-destructive, not idempotent, rate limits, CAPTCHA, dependency on a third-party API (BGPView), and variability of results. No contradiction with annotations.

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 description is a single paragraph that is front-loaded with purpose. It includes necessary details (rate limits, alternatives) without verbosity. Could be slightly more structured, but overall concise and to the point.

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?

Given the complexity (7 parameters, 1 required), the description covers purpose, usage, behavior, output (with output schema present), and limitations. It is complete for an AI agent to understand when and how to use the tool.

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 description coverage is 100%, so baseline is 3. The description does not add significant meaning beyond what the schema already provides for parameters. It mentions output fields (origin AS, AS-PATH, etc.) but not parameter-specific semantics.

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?

The description uses a specific verb ('Resolve') and resource ('IPv4/IPv6 address or CIDR prefix to live BGP routing data'), clearly stating the tool's purpose. It distinguishes from sibling tools by naming alternatives like network_asn_lookup, network_whois, and network_ip_geolocation.

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

Usage Guidelines5/5

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

Explicitly states when to use ('when you need the routing path / AS-PATH for an address') and provides alternatives for other use cases. Also mentions non-idempotent behavior and rate limits, offering clear guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server