Skip to main content
Glama

pbs_node_syslog

Fetch syslog entries from a PBS node. Specify node, limit, date range, line numbers, or service filter to retrieve relevant log lines.

Instructions

READ-ONLY: fetch syslog entries from a PBS node. Returns a list of {n, t} dicts (n=line number, t=text). For the systemd journal (with epoch/cursor filtering) use pbs_node_journal instead. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNoPBS node name (or 'localhost').localhost
limitNoMax number of syslog entries to return.
sinceNoDisplay log since this date-time string.
startNoStart line number.
untilNoDisplay log until this date-time string.
serviceNoFilter to one systemd service's lines.
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
Behavior3/5

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

Declares read-only and returns structured data, but with no annotations, the description should disclose more about edge cases (empty results, error conditions) and behavior limits.

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?

Two sentences, front-loaded with purpose and return format, no extra fluff. Every sentence earns its place.

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?

Adequate for a simple fetch tool with output schema, but lacks usage context for parameters like since/until format and pagination hints. Schema partially compensates.

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 covers 100% of parameter descriptions, so description adds no extra semantic value beyond what schema provides. Baseline score of 3 applies.

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?

Description explicitly states 'fetch syslog entries from a PBS node' and distinguishes from sibling pbs_node_journal by specifying alternative use case for systemd journal with epoch/cursor filtering.

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

Usage Guidelines4/5

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

Specifies read-only nature, provides alternative tool for systemd journal, and mentions config prerequisite. Lacks deeper guidance on parameters like limit vs start.

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