Skip to main content
Glama

Wait for a task

proxmox_wait_for_task
Read-only

Wait for a running Proxmox task to finish or time out, then return its outcome and log tail. Use it to track asynchronous cluster operations.

Instructions

Wait until a running task finishes (or the timeout passes) and return its outcome and log tail.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "upid": "<upid>"
    },
    "name": "proxmox_wait_for_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
upidYesTask ID (UPID), e.g. UPID:pve1:000A1B2C:0123ABCD:6701F3A2:qmstart:100:root@pam:
timeout_sNoHow long to wait in seconds (default PROXMOX_TASK_TIMEOUT_MS)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations establish only that this is a read-only, non-open-world operation; the description adds the key behavioral fact that the call blocks until completion or timeout, and that it yields both the outcome and a log tail. What remains undisclosed is what the caller gets back when the timeout fires — an error, a partial result, or a still-running marker.

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?

A single sentence with the blocking behavior and the return content front-loaded, and no filler. Nothing could be removed without losing information.

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?

There is no output schema, and the description compensates by naming what is returned (outcome and log tail), which is the essential missing piece. For a two-parameter blocking tool it is nearly complete, with only the timeout-exit behavior left unstated.

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 description coverage is 100%, including a UPID example and the PROXMOX_TASK_TIMEOUT_MS default for timeout_s, so the schema carries parameter meaning. The description's only added signal is the passing mention of 'the timeout', which merely echoes timeout_s without new syntax or constraints.

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 states a specific verb and resource: blocking until a running task finishes, plus returning its outcome and log tail. That is clearly distinguishable from a plain status fetch, but it never names proxmox_get_task or proxmox_get_task_log, so the agent must infer the difference from names alone.

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?

Usage is implied by the verb 'wait' — call it when you need the task to complete rather than a snapshot. There is no explicit statement of when to prefer a single-shot status check or log retrieval over blocking, and no guidance on choosing a timeout for long-running operations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools