Skip to main content
Glama
mhajder

librenms-mcp

by mhajder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Poller Group Get

poller_group_get
Read-onlyIdempotent

Retrieve a specific LibreNMS poller group by ID or name, or list all groups by omitting the parameter. Use an ID to fetch a group literally named 'all'.

Instructions

Get poller group(s) from LibreNMS.

Input Schema

NameRequiredDescriptionDefault
poller_groupNoPoller group ID or name. Omit (or pass 'all') to list every poller group; a group literally named 'all' must be fetched by its ID.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.12.0
    • addedInput schema / properties / poller_group / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / poller_group / default
      Added value: +null
    • changedInput schema / properties / poller_group / description
      Previous value: -"Poller group identifier or 'all'"New value: +"Poller group ID or name. Omit (or pass 'all') to list every poller group; a group literally named 'all' must be fetched by its ID."
    • removedInput schema / properties / poller_group / type
      Removed value: -"string"
    • removedInput schema / required
      Removed value: -[
-  "poller_group"
-]
  2. First observedv1.9.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that – no note on the list-all default behavior or result volume – so it contributes no extra behavioral context.

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 short, front-loaded sentence with no filler or repetition. It is appropriately sized for a one-parameter read tool, though it is terse enough to border on under-specification.

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?

With an output schema present, return values need not be described, and the single optional parameter is fully documented in the schema. Annotations cover safety, so the only real gap is the absence of usage context, which is minor for a simple getter.

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%, and the schema fully explains the optional poller_group parameter including the 'all' handling, so the description need not repeat it. Baseline 3 applies since the description adds no parameter meaning of its own.

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 gives a clear verb ('Get') and resource ('poller group(s)') scoped to LibreNMS, so an agent immediately knows it retrieves poller group records. It does not differentiate from siblings, but no other poller-group tool exists in the sibling list, so there is little to disambiguate.

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 offers no guidance on when to call this versus alternatives, nor any prerequisites or context (e.g., that it can be used to resolve a group name to an ID for other tool calls). The only usage hint lives in the parameter schema, not the description.

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