Skip to main content
Glama

bgp_sessions

Read-onlyIdempotent

Retrieve BGP session data from LibreNMS with filters for ASN, hostname, state, and more. Query specific sessions to monitor network routing status.

Instructions

List BGP sessions from LibreNMS with optional filters.

Returns: dict: The JSON response from the API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asnNoFilter by local ASN
limitNoMaximum number of results to return
offsetNoNumber of results to skip (offset) for pagination
hostnameNoFilter by device hostname
bgp_descrNoFilter by BGP description (SQL LIKE)
bgp_stateNoFilter by BGP state (e.g., established)
bgp_familyNoFilter by address family: 4 (IPv4) or 6 (IPv6)
remote_asnNoFilter by remote ASN
local_addressNoFilter by local IP address
bgp_adminstateNoFilter by admin state (start, stop, running)
remote_addressNoFilter by remote IP address

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. Description adds nothing beyond, but does not contradict.

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?

Two sentences, efficient, no filler. Includes return type information upfront.

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?

Tool has 11 optional params and output schema; description does not explain pagination or filtering in detail, but schema and annotations compensate. Adequate overall.

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%; description only adds 'with optional filters', which is redundant. No extra value beyond 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?

Clearly states verb 'List', resource 'BGP sessions', and source 'LibreNMS'. Distinguishes from sibling tools like bgp_session_get and bgp_session_edit.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., bgp_session_get for a single session) or any context-specific advice.

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/mhajder/librenms-mcp'

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