Skip to main content
Glama
mhajder

librenms-mcp

by mhajder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Switching Links

switching_links
Read-onlyIdempotent

List network links from LibreNMS with pagination to control result size, returning JSON data for monitoring and analysis.

Instructions

List all links from LibreNMS.

Returns: dict: The JSON response from the API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return
offsetNoNumber of results to skip (offset) for pagination

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.10.3
    • 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"
+}
  2. First observedv1.9.0

TDQS

B3.1/5.0
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, covering the safety profile. The description adds the fact that it returns 'the JSON response from the API' — which is low-value and somewhat obvious. No additional behavioral context (e.g., full-response format, no filtering) is provided beyond what annotations supply.

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 short and front-loaded with the core action. The returns line adds minimal value but doesn't waste much space. It could be improved by stating that the JSON is returned as a dict, which it does — but that's close to trivial.

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?

Given the simple 2-parameter list operation and rich annotations (read-only, idempotent), the description is mostly complete. However, it lacks any clarification of what 'links' means or how pagination behaves end-to-end, and the presence of an output schema reduces the need to describe return structure. Minor gaps keep it from being higher.

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% — both limit and offset are documented with defaults and descriptions in the schema. The tool description adds no new parameter semantics. Baseline 3 is appropriate since the schema fully handles parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb and resource: 'List all links from LibreNMS.' This is serviceable, though 'links' is ambiguous in a network monitoring context (physical links, port links, etc.). From the sibling tools (device_links, switching_vlans) it can be inferred to be switching/LLDP-style links, but the description doesn't disambiguate on its own.

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?

The description implies it lists all links, which signals a broad list operation. However, there is no explicit guidance on when to choose this over siblings like device_links or ports_list. The pagination parameters (limit/offset) imply list usage, but no alternatives or exclusions are mentioned.

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