Skip to main content
Glama

pbs_tasks_list

List PBS tasks on a node, with optional filters for active or failed tasks.

Instructions

List PBS tasks on a node (read). Defaults to 'localhost' (standard single-node PBS name). Optionally filter: running=True for active tasks, errors=True for failed tasks. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNolocalhost
limitNo
errorsNo
runningNo
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?

No annotations are provided, so the description must convey behavioral traits. It indicates the tool is read-only and requires configuration, but does not disclose return format, pagination, error handling, or any side effects. Basic transparency is present but incomplete.

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?

The description is concise at 3 sentences, front-loading the purpose. Every sentence provides essential information without redundancy.

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?

Given the tool is a simple list operation with 5 parameters and an output schema exists, the description covers the core function and key filters. It lacks details on pagination or edge cases, but the output schema reduces the need for that. Nearly complete for its complexity.

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 low (20%), and the description adds meaning for node, running, and errors parameters, clarifying their use. However, limit and proximo_target are not discussed, and the config requirement is mentioned but not explicitly linked to proximo_target. Partial compensation but not full.

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 clearly states 'List PBS tasks on a node (read)', specifying the verb, resource, and scope. It distinguishes as a read operation but does not explicitly differentiate from sibling list tools like pbs_jobs_list, though the context of PBS tasks is unique. Clarity is high but sibling differentiation is absent.

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

Usage Guidelines3/5

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

The description provides guidance on default node and optional filters for running and errors, which helps in selecting parameters. However, it does not explain when to use this tool over alternatives (e.g., pbs_jobs_list vs pbs_tasks_list) or mention any prerequisites beyond configuration.

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