Skip to main content
Glama

pve_node_journal

Retrieve systemd journal entries from a Proxmox VE node for log inspection. Filter by time range and limit to the most recent lines.

Instructions

READ-ONLY: fetch systemd journal lines from a PVE node for log inspection.

No state change. Returns a list of journal-line strings. Narrow with since/until (timestamp format per PVE — typically epoch seconds or ISO 8601) and lastentries (most-recent N, max 5000; higher is rejected with an error). For the classic syslog view use pve_node_syslog; for one service's current state use pve_node_service_status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNoPVE node name; defaults to the configured node
sinceNoOnly return entries at or after this timestamp (journalctl-compatible format)
untilNoOnly return entries at or before this timestamp (journalctl-compatible format)
lastentriesNoNumber of most-recent journal lines to return, max 5000 (values above are rejected)
proximo_targetNoWhich configured Proxmox target to run this call against — a target name from your multi-target config (a specific PVE/PBS/PMG/PDM box). Omit to use the single/default target from the environment; the selection applies only to this call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, description fully discloses read-only nature, no state change, return type, and error condition for lastentries > 5000.

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?

Extremely concise: two sentences for purpose and parameters, one for sibling differentiation. Front-loaded with essential information, no redundant text.

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?

Fully covers all aspects needed for correct selection and invocation: purpose, read-only guarantee, parameters with constraints, siblings, and output expectation. Output schema exists to cover return values.

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

Parameters5/5

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

Adds meaning beyond schema: explains timestamp formats (epoch or ISO 8601), default node behavior, and lastentries cap with error on rejection. Schema covers 100% but description enriches with usage details.

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?

Clearly states it fetches systemd journal lines from a PVE node, is read-only, and returns a list of strings. Distinguishes from sibling tools pve_node_syslog and pve_node_service_status.

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?

Explicitly says when to use this tool vs alternatives, provides parameter guidance for since/until format and lastentries limit, and notes error behavior for exceeding max.

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/john-broadway/proximo'

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