Skip to main content
Glama
mhajder

librenms-mcp

by mhajder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Devicegroup Devices

devicegroup_devices
Read-onlyIdempotent

Retrieve devices from a LibreNMS device group by name. Supports full device data and pagination for large groups.

Instructions

List devices in a device group from LibreNMS.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fullNoSet to true to get complete device data instead of just IDs
nameYesDevice group name
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
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, fully covering the safety profile. The description adds no behavioral context beyond the bare 'List' — it does not mention that full=true changes the return shape or that limit/offset control pagination, though those details live in the schema. With the bar lowered by annotations, the description still contributes nothing extra, so a modest score is warranted.

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?

One sentence of eight words with zero waste, and the verb 'List' is front-loaded. There is nothing to trim, and the terseness is proportionate for a simple read operation.

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?

The definition benefits from rich structured data: an output schema documents return values, annotations cover the safety profile, and the schema fully documents parameter semantics. The only notable gap is routing guidance between this and the large sibling set, especially devices_list and the devicegroup mutation tools. For a low-complexity read tool, this is largely complete.

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 all four parameters (name, full, limit, offset) documented in the input schema, so the baseline 3 applies. The description itself adds no parameter detail, but none is needed since the schema carries the load. No enums or complex types require further explanation.

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+resource: 'List devices in a device group from LibreNMS.' The scoping 'in a device group' clearly sets it apart from a generic device listing, and the verb 'List' is unambiguous. It does not explicitly name sibling alternatives like devices_list or devicegroup_add_devices, so it stops short of a 5.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention devices_list for unfiltered device queries, nor devicegroup_add_devices/remove_devices for membership modification. An agent must infer usage purely from the tool name and schema.

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