librenms-mcp

Overview Schema Source Related Servers Discussions Admin

Logs Authlog

logs_authlog

Read-onlyIdempotent

Retrieve authentication logs from LibreNMS across the entire server, with optional time range, pagination, and sort controls for auditing login activity.

Instructions

Get authentication logs from LibreNMS.

Auth logs are server-wide rather than per-device, so this takes no hostname.

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)
`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

A4.5/5.0

Behavior4/5

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

Annotations already establish readOnly, idempotent, and non-destructive behavior. The description adds useful context by revealing that auth logs are global across the server, which explains why there is no hostname filtering. This goes beyond what the annotations alone convey.

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?

Two short sentences with no filler. The action is front-loaded and the scope clarification is concise and relevant.

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?

With full schema descriptions, a true output schema, and safety annotations, the description covers the essential invocation context. The server-wide/no-hostname note addresses the one subtlety that could otherwise lead to a wrong call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so parameters are already well documented. The description adds meaning by explicitly stating that the tool takes no hostname because auth logs are server-wide, helping an agent avoid expecting a device-scoped parameter.

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 and resource: 'Get authentication logs from LibreNMS.' It also distinguishes itself from sibling log tools by noting auth logs are server-wide and take no hostname, making its scope clear.

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

Usage Guidelines4/5

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

The description clearly states the context for use: authentication logs are server-wide rather than per-device, so no hostname should be passed. It does not explicitly name sibling alternatives such as logs_eventlog or logs_syslog, but the scoping guidance is clear.

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

Deploy Server