Skip to main content
Glama
mhajder

librenms-mcp

by mhajder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Alert Rules List

alert_rules_list
Read-onlyIdempotent

List all LibreNMS alert rules with configurable pagination, returning structured JSON to support monitoring, review, and automated analysis of alert conditions.

Instructions

List all alert rules 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

C2.9/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 covered. The description adds only that it comes from LibreNMS and returns a dict, but it fails to disclose that the list is paginated via limit/offset, which contradicts the literal 'List all' claim and could mislead an agent about the full result set.

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 appropriately short and front-loaded with the core action. The 'Returns: dict' line is low-value filler because an output schema exists, but it does not significantly hurt readability or structure.

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?

For a simple read-only list with two optional parameters and a safe annotation profile, the description is minimally viable. The main gaps are the missing pagination caveat and lack of sibling differentiation, both of which matter for correct invocation when agents need 'all' rules or need to distinguish alert rules from alerts.

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 documented, so the baseline is 3. The description adds no additional meaning about when to adjust these parameters or how pagination interacts with the 'all' claim, but it does not need to compensate for missing schema info.

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 verb and resource: 'List all alert rules from LibreNMS.' It is clear that this tool lists alert rules rather than individual alerts or template rules, so it is distinguishable in intent. However, it does not explicitly differentiate itself from sibling list/get tools, and 'all' is slightly misleading given the pagination parameters.

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 gives no guidance about when to use this tool versus alternatives such as alert_rule_get, alerts_get, or alert_templates_list. It does not mention when-not-to-use, exclusions, or any conditions that would route an agent to a sibling tool.

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