Skip to main content
Glama
claude-proxmox-controller

claude-proxmox-controller

task_log

Read-onlyIdempotent

Retrieve a Proxmox task’s log by host and UPID to inspect backup progress or errors; use the start line to resume reading long logs.

Instructions

A task's log (a backup's progress, an error).

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>",
      "upid": "<upid>"
    },
    "name": "task_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesThe host's id, from list_hosts.
upidYesThe task's UPID.
startNoLine to start from (for long logs).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds only that the log content may be progress output or an error, which is mildly useful context about the return content but does not address log size, truncation, or how to page through long output.

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

Conciseness3/5

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

There is zero padding, but the whole description is a single sentence fragment rather than a front-loaded statement of purpose plus usage. Brevity here reflects under-specification rather than disciplined editing.

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 retrieval tool with full schema coverage and strong annotations, the essentials are present, and an output schema is not needed. However, the description omits how to obtain a UPID or host id and does not explain that 'start' enables iterating over long logs, leaving the agent to reconstruct the workflow.

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%, and the schema already documents host ('from list_hosts'), upid, and start ('Line to start from'). The description adds no meaning beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource (a task's log) and illustrates its content with parenthetical examples ('a backup's progress, an error'), but it is a noun phrase with no verb, so the agent must infer that the tool retrieves the log rather than something else about it. It is distinguishable from 'stop_task' but only loosely.

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?

There is no when-to-use guidance at all: nothing says to call this after starting or failing a task, nothing points to where a UPID comes from, and no alternative (e.g., a task-status tool) is named or excluded. The agent must infer the call context from the required parameters alone.

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