Skip to main content
Glama

pve_tasks_list

List recent tasks from a Proxmox node, filtered by type, status, or VM ID, with a limit up to 1000.

Instructions

List recent tasks on a node (read). limit 1-1000 (clamped).

Caveat: this is a windowed, per-node slice — node defaults to the configured node, and only the limit most-recent tasks return. A task on another node or outside the window is absent without being dead. Never conclude a backup failed from absence here — verify against pve_backup_list or pbs_snapshots_list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNo
vmidNo
limitNo
errorsNo
typefilterNo
statusfilterNo
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?

No annotations provided, so description carries full burden. Discloses windowed nature, per-node scope, limit clamping (1-1000), and absence behavior. Could mention ordering or empty results, but overall adequate. No contradiction with missing annotations.

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 plus a caveat. Front-loaded with purpose. Every sentence adds value with no fluff. Meets high standard for conciseness.

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?

Has output schema so return values not needed. But with 7 parameters and low schema coverage, description should explain more parameter behavior. Caveat about backup is helpful but incomplete for overall parameter documentation. Missing explanation of 'configured node' context.

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

Parameters2/5

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

Schema description coverage is only 14%, but description only adds info on 'limit' (clamped) and 'node' (defaults to configured). Does not explain 'vmid', 'errors', 'typefilter', 'statusfilter', 'proximo_target'. Fails to compensate for low schema coverage.

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 'List recent tasks on a node (read)', identifies resource (tasks on a node), verb (list), and read-only nature. Distinguishes from sibling tools like pve_backup_list and pbs_snapshots_list by warning not to infer backup failure from absence.

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 states caveats: windowed per-node slice, limit clamping, node defaults to configured node. Provides direct guidance on when not to use (for backup verification) and suggests alternative tools (pve_backup_list, pbs_snapshots_list).

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