librenms-mcp

Overview Schema Source Related Servers Discussions Admin

Logs Syslog

logs_syslog

Read-onlyIdempotent

Retrieve syslog entries from LibreNMS for a device or all devices, filtered by hostname and time range, with pagination and sort order control.

Instructions

Get syslogs 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

C2.7/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: no mention of pagination behavior, no note that timestamps can be Unix or datetime strings, no hint about result ordering or volume. With annotations carrying the burden, the description contributes almost 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 sentence with no filler and the core action front-loaded. Nothing is wasted, but its brevity is a byproduct of under-specification rather than disciplined editing.

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?

An output schema exists, so return values need not be described, and all parameters are documented in the schema. What remains missing is any guidance on the tool's place among the four sibling log endpoints and its device-scoping behavior, which is the main ambiguity an agent would face.

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 adds no parameter-level meaning beyond restating that results are device-scoped, and even that conflicts slightly with the schema's note that omitting hostname returns all devices. Baseline 3 is appropriate when the schema does the work.

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

Purpose3/5

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

The description states a verb (Get) and resource (syslogs) plus a source system (LibreNMS), so the basic operation is identifiable. However it makes no attempt to distinguish this tool from closely named siblings such as logs_authlog, logs_eventlog, logs_alertlog, or especially logs_syslogsink, which an agent could easily confuse. This places it above a tautology but below a definition that cleanly separates it from alternatives.

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?

There is no guidance on when to choose this tool versus the other log tools (authlog, eventlog, alertlog, syslogsink) or when a syslog query is appropriate at all. No prerequisites, no exclusions, no alternatives are named. The agent must infer usage entirely from the name.

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

Deploy Server