Skip to main content
Glama
mhajder

librenms-mcp

by mhajder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Routing Ip Addresses

routing_ip_addresses
Read-onlyIdempotent

Retrieve IP addresses monitored by LibreNMS with optional limit and offset for paginated results.

Instructions

List all IP addresses 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.2/5.0
Behavior3/5

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

Annotations already provide the read-only/idempotent/non-destructive safety profile, so the description only needs to add scoping context; it does note the LibreNMS source and JSON dict return. It does not disclose that the default limit is 100 or that 'all' is only achieved through pagination, which is a notable gap for a listing tool.

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, front-loaded with the main behavior, and free of filler. The 'Returns' line is somewhat redundant given the output schema, but it is minor and does not hurt usability.

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?

For a low-complexity, two-optional-parameter listing tool with full schema coverage, an output schema, and safety annotations, the description is sufficient for an agent to select and invoke it. The main omission, pagination behavior, is partially covered by the parameter descriptions but deserves more explicit mention.

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%, with limit and offset already fully documented, so the description adds no parameter-level meaning. A baseline of 3 is appropriate because the schema carries the load and the description does not compensate.

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?

The description states a specific action ('List all IP addresses') and a source system ('LibreNMS'), making the tool's core function clear. However, the 'routing' qualifier in the name is not explained and sibling tools such as port_ip_info, arp_search, and fdb_lookup are not differentiated, so it is not a fully distinctive definition.

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 is given for when to use this tool instead of related IP/address-oriented siblings, and there is no mention of pagination or scale considerations even though the schema includes limit and offset. The agent must infer usage entirely from the schema and context.

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