Skip to main content
Glama
claude-proxmox-controller

claude-proxmox-controller

list_tasks

Read-onlyIdempotent

Retrieves a host's recent tasks, newest first, including each task's final status so you can review Proxmox activity and outcomes.

Instructions

The host's recent tasks, newest first, with how they ended.

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": {
      "host": "<host>"
    },
    "name": "list_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesThe host's id, from list_hosts.
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

The annotations already establish that this is a safe, idempotent read operation. The description usefully adds ordering and that results include how tasks ended, but it does not explain what counts as 'recent', how retention works, or how limit affects the result.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no wasted wording. It is appropriately sized overall, though its compactness leaves 'recent' undefined.

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?

For a simple read-only list tool, the annotations cover safety and the description gives some return context. However, without an output schema and with limit behavior plus the 'recent' window still unclear, an agent lacks full invocation 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?

The host parameter is documented in the schema as coming from list_hosts, but the limit parameter has no schema description and the tool description adds no meaning about truncation or defaults. With only 50% schema coverage, the description fails to compensate for the undocumented limit.

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 identifies the resource as the host's recent tasks and adds ordering (newest first) and outcome detail (how they ended). It lacks an explicit verb, but the tool name supplies it and the resource scope is clear enough to distinguish from backup/job listing siblings.

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

Usage Guidelines2/5

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

The description provides no when-to-use guidance, no exclusions, and no alternatives. With many sibling list tools available, an agent gets no explicit routing help beyond the phrase 'host's recent tasks'.

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