Skip to main content
Glama

Read node syslog

proxmox_get_node_syslog
Read-only

Read a Proxmox node's system log as syslog lines, filtered by service and time range, with pagination via start and limit.

Instructions

Read a node's system log (journal rendered as syslog lines), optionally for one service and a time range. Page with start/limit. For the raw systemd journal with 'last N lines' semantics use proxmox_get_node_journal.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "proxmox_get_node_syslog"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeNoNode name. Defaults to PROXMOX_DEFAULT_NODE, or the only node on a single-node install. See proxmox_list_nodes.
limitNoMaximum number of results (default 200)
sinceNoStart time, e.g. '2026-01-31 08:00:00' or 'yesterday'
startNoLine offset to start from (default 0)
untilNoEnd time, same format as since
searchNoCase-insensitive substring filter on names, IDs, tags and similar fields
serviceNoOnly this service/unit, e.g. pveproxy, pvedaemon, corosync, pve-cluster

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine behavioral context beyond that: the log is a journal rendered as syslog lines, and result sets are paged via start/limit. It does not mention default page size (200) or any throttling, which keeps it from a 5.

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?

Three short sentences, front-loaded with the purpose, then pagination, then the disambiguation pointer. Every clause carries information and nothing is repeated from the schema.

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 seven-parameter read-only log tool with no output schema, the description covers what the data is, how to filter, how to page, and which sibling to prefer. Only minor gaps remain, such as default result count and the exact line format returned.

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 seven parameters including node defaulting, since/until formats, and service examples are already documented. The description only adds the framing that start/limit are the pagination pair, which is marginal value over the schema.

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?

States a specific verb and resource ('Read a node's system log') plus the output shape ('journal rendered as syslog lines'), and explicitly contrasts itself with proxmox_get_node_journal. An agent can distinguish it from the journal sibling without opening either schema.

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

Usage Guidelines5/5

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

Gives the routing rule directly: use this for syslog-line style reads with service/time-range filtering, and use proxmox_get_node_journal when 'last N lines' raw journal semantics are wanted. The alternative and the condition that selects it are both named.

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