Skip to main content
Glama

pve_task_status

Retrieve the current status of a Proxmox task by its UPID. Returns running or stopped state and exit status for polling long-running operations.

Instructions

READ-ONLY: get an async Proxmox task's status by its UPID — running vs stopped, plus the exit status once it has finished.

No state change. Use it to poll long-running ops (migrate, snapshot, rollback, backup) that return a UPID. Returns a dict with status and exitstatus. To block until the task completes use pve_task_wait, and for its log output use pve_task_log. Pass node for a task on a non-default node; omitting it falls back to the configured default node (the UPID is not parsed for the node).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNoPVE node the task is running on. Omit to resolve it automatically.
upidYesProxmox task UPID (unique process ID) returned by an async operation.
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?

The description explicitly states 'READ-ONLY' and 'No state change', and describes the return value (dict with status and exitstatus). It also explains the fallback behavior for the node parameter. No annotations are provided, so the description fully carries the burden and does so well.

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 (about 70 words) and well-structured: starts with a one-line summary, then provides use cases, alternatives, and parameter details. Every sentence adds value with no redundancy.

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 existence of an output schema and full parameter schema coverage, the description is complete. It covers purpose, usage guidelines, behavioral transparency, and parameter semantics adequately for an agent to select and invoke the tool correctly.

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

Parameters4/5

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

The schema has 100% coverage with descriptions for all three parameters. The description adds value by explaining the node fallback behavior (omitting it uses default node, UPID not parsed) and the purpose of proximo_target (multi-target config). This goes beyond the schema but is not extensive.

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?

The description clearly states that the tool retrieves the status of an async Proxmox task by its UPID, distinguishing it from siblings like pve_task_wait and pve_task_log. It specifies that it is read-only and lists example use cases (migrate, snapshot, rollback, backup).

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?

The description explicitly says to use this tool for polling long-running operations that return a UPID, and provides alternatives: pve_task_wait for blocking and pve_task_log for log output. It also explains when to pass the `node` parameter.

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