librenms-mcp

Overview Schema Source Related Servers Discussions Admin

Logs Alertlog

logs_alertlog

Read-onlyIdempotent

Retrieve LibreNMS alert logs for a device or all devices, with optional time-range filters, pagination, and sorting to review alert history.

Instructions

Get alert logs for a device from LibreNMS.

Input Schema

Name	Required	Description
`limit`	No	Maximum number of results to return
`start`	No	Number of results to skip (offset) for pagination
`to_ts`	No	End timestamp filter (Unix timestamp or datetime string)
`from_ts`	No	Start timestamp filter (Unix timestamp or datetime string)
`hostname`	No	Device hostname or ID. Omit for entries from all devices.
`sortorder`	No	Sort order: ASC or DESC

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.12.0Oct 15, 2026

addedInput schema / properties / hostname / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / hostname / default
```
Added value: +null
```

changedInput schema / properties / hostname / description

Previous value: -"Device hostname or ID"New value: +"Device hostname or ID. Omit for entries from all devices."

removedInput schema / properties / hostname / type
```
Removed value: -"string"
```
removedInput schema / required
```
Removed value: -[
-  "hostname"
-]
```

Changed9 schema fields changedv1.10.3Jul 12, 2026
- removedInput schema / properties / limit / anyOf
```
Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]
```
- changedInput schema / properties / limit / default
```
Previous value: -nullNew value: +100
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- addedInput schema / properties / limit / type
```
Added value: +"integer"
```
- removedInput schema / properties / start / anyOf
```
Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]
```
- changedInput schema / properties / start / default
```
Previous value: -nullNew value: +0
```
- changedInput schema / properties / start / description
```
Previous value: -"Page number for pagination"New value: +"Number of results to skip (offset) for pagination"
```
- addedInput schema / properties / start / minimum
```
Added value: +0
```
- addedInput schema / properties / start / type
```
Added value: +"integer"
```
First observedv1.9.0May 27, 2026

TDQS

B3.3/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, so the safety profile is fully covered without the description. The description adds only that the source is LibreNMS and that retrieval is device-oriented, which is modest context beyond the structured fields.

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?

A single front-loaded sentence with no filler; the action and resource lead immediately and nothing is wasted.

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?

Return values need not be described since an output schema exists, and parameters are fully covered. The remaining gap is the failure to position this tool against its many log-fetching siblings, leaving the agent to infer which log endpoint to call.

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%, so all six parameters (limit, start, to_ts, from_ts, hostname, sortorder) are already documented in the schema. The description's 'for a device' loosely maps to hostname but adds no format, default, or pagination detail beyond what the schema provides; baseline 3 is appropriate.

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 (Get) and resource (alert logs) scoped to a device from LibreNMS, so the operation is unambiguous. However, it does not distinguish itself from near-identical siblings like logs_eventlog, logs_syslog, and logs_authlog, which share the same verb+resource pattern.

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 on when to choose this over the other log tools (logs_eventlog, logs_syslog, logs_authlog). The phrase 'for a device' implies device scoping, but hostname is optional and no conditions or alternatives are named.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server