Skip to main content
Glama
mhajder

librenms-mcp

by mhajder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Bgp Sessions

bgp_sessions
Read-onlyIdempotent

List BGP sessions from LibreNMS and filter them by ASN, hostname, state, address family, or IP address. Supports pagination for large result sets.

Instructions

List BGP sessions from LibreNMS with optional filters.

Input Schema

NameRequiredDescriptionDefault
asnNoFilter by local ASN
limitNoMaximum number of results to return
offsetNoNumber of results to skip (offset) for pagination
hostnameNoFilter by device hostname or ID. An unknown device returns an error.
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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.12.0
    • changedInput schema / properties / hostname / description
      Previous value: -"Filter by device hostname"New value: +"Filter by device hostname or ID. An unknown device returns an error."
  2. Changed5 schema fields changedv1.10.3
    • changedInput schema / properties / asn / anyOf
      Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / bgp_family / anyOf
      Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 100,
+  "description": "Maximum number of results to return",
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Number of results to skip (offset) for pagination",
+  "minimum": 0,
+  "type": "integer"
+}
    • changedInput schema / properties / remote_asn / anyOf
      Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
  3. First observedv1.9.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered structurally. The description adds nothing behavioral beyond that — no mention of pagination behavior, default result size, or what happens with zero matches, so it earns little credit.

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?

A single front-loaded sentence with zero waste. It is efficient, though the brevity borders on under-specification rather than tight, purposeful concision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and full schema coverage, the return shape and parameters are covered elsewhere, so the description needn't repeat them. However, for an 11-parameter listing tool it should at least hint at filter combination behavior or pagination defaults, which it omits.

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 all 11 parameters (including filter semantics like SQL LIKE for bgp_descr and family 4/6 for bgp_family) are already documented in the schema. The description's generic 'optional filters' adds no meaning beyond it; baseline 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?

States a specific verb and resource ('List BGP sessions from LibreNMS') plus the scope qualifier 'with optional filters'. This distinguishes it from siblings like bgp_session_get and bgp_session_edit by implication (plural list vs. single fetch vs. edit), but no sibling is named explicitly.

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?

Only says 'with optional filters' — it never says when to use this list tool versus bgp_session_get or bgp_session_edit, nor any exclusions. Usage is barely implied, with no routing guidance for an agent choosing among BGP tools.

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

Deploy Server

Other Tools