librenms-mcp

Overview Schema Source Related Servers Discussions Admin

Logs Eventlog

logs_eventlog

Read-onlyIdempotent

Retrieve event logs for a device from LibreNMS by hostname, with optional time range, sort order, and pagination controls to isolate relevant network events.

Instructions

Get event logs for a device from LibreNMS.

Input Schema

TableJSON 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`	Yes	Device hostname or ID
`sortorder`	No	Sort order: ASC or DESC

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

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

A3.9/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 covered. The description adds 'for a device from LibreNMS' as extra context, but does not disclose behavioral details such as pagination defaults, time-filter semantics, or sort behavior beyond what structured fields already provide.

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?

The description is a single, front-loaded sentence with no filler or redundant restatement. It communicates the core purpose efficiently and is easy for an agent to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that the input schema fully documents all six parameters, an output schema exists, and annotations cover the read-only, idempotent, non-destructive behavior, the brief description is complete. No critical information needed for correct invocation is missing.

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 every parameter has a descriptive comment, so the baseline is 3. The description itself adds no parameter-specific meaning, but the schema already carries that burden adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Get') with a clear resource ('event logs') and scope ('for a device'), and identifies the source system (LibreNMS). This distinguishes it from sibling log tools like logs_syslog or logs_authlog by naming the event-log resource.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the use case of retrieving event logs for a device, giving some context, but provides no explicit guidance on when to choose this tool over sibling log tools, nor any exclusions or alternatives. Selection criteria are left to inference.

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

Deploy Server