Skip to main content
Glama
mhajder

librenms-mcp

by mhajder
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

Logs Syslog

logs_syslog
Read-onlyIdempotent

Retrieve syslog messages for a network device from LibreNMS, with optional time range, pagination, and sorting filters to locate specific events.

Instructions

Get syslogs 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. Dates show when Glama detected each change.

  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

B3.4/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 no behavioral context beyond the factual resource and scope, but it also does not contradict the annotations. No annotation contradiction.

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 one short sentence with no filler, front-loading the verb and resource. Every word contributes: 'Get syslogs for a device from LibreNMS' is minimally sufficient at this level.

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?

With a full input schema, an output schema, and read-only/idempotent annotations, the description covers the operational essentials for calling the tool. It is slightly less complete than ideal because it does not hint at pagination/time-filter behavior or differentiate from the similarly named sibling, though these are inferable from the schema.

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 each parameter has a clear description and default. The tool description does not need to restate parameter details; the baseline 3 applies because the schema carries the semantic load.

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'), a distinct resource ('syslogs'), and a scope ('for a device'), which clearly identifies what the tool does. It does not explicitly contrast itself with sibling log tools like logs_syslogsink, 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 Guidelines2/5

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

There is no guidance about when to use this tool versus logs_eventlog, logs_alertlog, logs_authlog, or logs_syslogsink. The phrase 'for a device' weakly implies device-scoped syslog retrieval, but no exclusions or alternative conditions are stated.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mhajder/librenms-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server