Skip to main content
Glama

Read node systemd journal

proxmox_get_node_journal
Read-only

Read a Proxmox node's systemd journal for recent entries or a time range, filtered by unit, identifier, priority, kernel messages, or text. Use it to diagnose node and service issues.

Instructions

Read a node's systemd journal: the last N entries (default 100) or a time range, optionally only one unit, a syslog identifier, a priority level or kernel messages.

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_journal"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeNoNode name. Defaults to PROXMOX_DEFAULT_NODE, or the only node on a single-node install. See proxmox_list_nodes.
unitNoOnly this systemd unit, e.g. pveproxy (.service implied)
sinceNoStart of the range: epoch seconds or a date like "2026-01-31 12:00:00" / ISO 8601
untilNoEnd of the range: epoch seconds or a date like "2026-01-31 12:00:00" / ISO 8601
kernelNoOnly kernel messages
searchNoCase-insensitive substring filter on names, IDs, tags and similar fields
priorityNoOnly this priority or more severe: 0 (emerg) .. 7 (debug), or a range 'LOW..HIGH'; e.g. 3 for errors
identifierNoOnly messages whose syslog identifier matches this glob, e.g. 'pve*'
lastentriesNoOnly the last N entries (default 100 when no range is given)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and idempotentHint=false, so safety is covered; the description adds no behavior beyond that. It does not say what the entries look like, whether large lastentries values are expensive, whether journal access needs elevated privileges, or why repeated calls are non-idempotent.

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 front-loaded sentence that moves from the verb to the selection mode to the optional filters, with no filler. The trailing filter enumeration grows long but each item maps to a real parameter.

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?

For a nine-parameter read tool with no output schema, the description covers the selection model and defaults adequately. It leaves open the output shape (raw journal lines vs structured entries) and the overlap with the syslog sibling, which an agent needs in order to call this correctly.

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 schema already documents node defaults, glob syntax for identifier, priority ranges, and the epoch/ISO date formats. The description repeats the filter list and the default of 100 without adding syntax or interaction rules (for example, what happens when since/until are combined with lastentries), so the baseline of 3 applies.

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 names a specific verb and resource ('Read a node's systemd journal') and enumerates the selection modes (last N entries or a time range) plus the filter dimensions. It is clear on its own, but it does not differentiate itself from the sibling proxmox_get_node_syslog, which reads the same conceptual data source.

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 reach for this tool versus proxmox_get_node_syslog or proxmox_get_node_report, and no note on prerequisites or typical investigative scenarios. The reader must infer usage from the purpose statement alone.

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