Skip to main content
Glama
mhajder

librenms-mcp

by mhajder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Logs Alertlog

logs_alertlog
Read-onlyIdempotent

Retrieve alert logs for a specific device from LibreNMS. Filter by time range, paginate, and sort results to investigate past alerts and troubleshoot network issues.

Instructions

Get alert logs for a device from LibreNMS.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return
startNoNumber of results to skip (offset) for pagination
to_tsNoEnd timestamp filter (Unix timestamp or datetime string)
from_tsNoStart timestamp filter (Unix timestamp or datetime string)
hostnameYesDevice hostname or ID
sortorderNoSort order: ASC or DESC

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.10.3
    • 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"
  2. First observedv1.9.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds only modest behavioral context by framing the call as device-scoped log retrieval; it does not describe ordering, filter semantics, or anything unusual, but no contradiction exists.

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 a single front-loaded sentence with no filler or repetition. It is concise, though it is also minimal enough that it leaves usage and differentiation to other dimensions.

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

Completeness4/5

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

For a simple read query with full schema coverage, an output schema, and read-only annotations, the short description is mostly sufficient. The main missing piece is sibling disambiguation (e.g., vs alerts_get or logs_eventlog), which prevents a 5.

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 the parameters (limit, start, from_ts, to_ts, hostname, sortorder) are fully documented in the input schema. The description itself adds no parameter-level meaning, but the schema carries the burden.

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 uses a specific verb ('Get'), resource ('alert logs'), and scope ('for a device'), so an agent can identify what the tool does. It doesn't explicitly contrast with alert_get_by_id, alerts_get, or the other logs_* siblings, so it stops short of full differentiation.

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 phrasing implies the tool is for historical alert logs scoped to one device, which gives the agent a reasonable usage context. However, it does not state when to choose it over alerts_get/alert_get_by_id or mention any exclusions or alternatives.

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