Skip to main content
Glama
tiancode
by tiancode

pve_list_tasks

Read-only

List recent tasks from Proxmox VE, sorted newest first. Filter by node, limit results, or show only failed tasks.

Instructions

List recent tasks, newest first.

    Applies to: task history. If ``node`` is given, lists that node's tasks;
    otherwise aggregates across all nodes. ``limit`` caps the number of
    entries returned; ``errors_only`` keeps only failed tasks.

    Returns a JSON list with ``upid``, ``type``, ``id`` (often the vmid),
    ``user``, ``status`` (final status / "OK"), ``starttime``/``endtime``
    (+human). Source: GET /nodes/{node}/tasks.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNo
limitNo
errors_onlyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description adds significant behavioral context beyond the readOnlyHint annotation: it specifies the order (newest first), aggregation behavior, and the exact fields returned (upid, type, id, user, status, starttime/endtime). No contradictions with 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?

The description is concise (3 sentences) and front-loads the core purpose. Every sentence adds value without unnecessary fluff.

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, the description provides enough context: it lists the return fields and explains behavior for all parameters. It is complete for a read-only listing tool.

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

Parameters5/5

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

Schema coverage is 0%, so the description fully compensates by explaining each parameter: node filters by node, limit caps entries, errors_only filters to failed tasks. This adds meaning beyond the schema property names.

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 'List recent tasks, newest first' and specifies it applies to task history. It differentiates from sibling tools like pve_task_status by describing aggregation across nodes and the specific resource (task history).

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?

The description explains when to use the node parameter (to filter by node) and the roles of limit and errors_only. However, it does not explicitly mention when not to use this tool or suggest alternatives for specific tasks.

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/tiancode/pve-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server