Skip to main content
Glama

pbs_node_task_log

Retrieve paginated log output for a PBS task by UPID. Use start and limit to navigate through logs without overwhelming responses.

Instructions

READ-ONLY: retrieve a PBS task's log output by UPID, paginated via start/limit. Use pbs_tasks_list to find UPIDs, or pbs_node_task_status for the terminal status only. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNoPBS node name (or 'localhost').localhost
upidYesThe task's Unique Process ID (UPID) string.
limitNoMax number of log lines to return.
startNoLine offset to start returning log output from (for pagination).
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
Behavior4/5

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

Description labels the tool as 'READ-ONLY' and describes pagination behavior via start/limit. With no annotations, it effectively communicates safety and operation, though could note error handling or output 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 concise sentences, each providing essential information. No wasted words; purpose, pagination, usage guidance, and prerequisites are efficiently communicated.

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?

Given the presence of an output schema and sibling tools, the description covers all necessary context: purpose, pagination, usage flow, and prerequisites. Complete for a log retrieval tool.

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 coverage is 100%, so parameters are well-documented. Description confirms pagination purpose for start/limit and relates upid to pbs_tasks_list, but adds limited new semantics beyond 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?

Clearly states 'retrieve a PBS task's log output by UPID' with pagination, and distinguishes from sibling tools pbs_tasks_list and pbs_node_task_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 directs when to use this tool versus pbs_tasks_list (to find UPIDs) and pbs_node_task_status (for terminal status). Also mentions prerequisite config 'Needs PROXIMO_PBS_* config'.

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