Skip to main content
Glama

Read task log

proxmox_get_task_log
Read-only

Read a Proxmox VE task log with paging from the start, or return the last lines by setting tail, to inspect task progress and errors.

Instructions

Read a task's log, paging from the start (or the end with tail=true).

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_get_task_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
tailNoReturn the last `limit` lines instead
upidYesTask ID (UPID), e.g. UPID:pve1:000A1B2C:0123ABCD:6701F3A2:qmstart:100:root@pam:
limitNoNumber of lines (default 500)
startNoFirst line (0-based, default 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description usefully adds that paging proceeds from the start unless tail=true, which is real behavioral context; however, it says nothing about large-log truncation, whether the log is complete or partial, or what a tail read implies for ordering.

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 core action front-loaded and the non-default branch (tail) parenthetically appended. No filler or redundancy.

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?

With no output schema, the description carries some burden for explaining the return value, yet it does not say what the log lines look like, whether line numbers or a truncation marker are included, or how partial results are signaled. For a simple read tool with fully documented parameters this is adequate but not complete.

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%, so upid, limit, start and tail are all documented in structured fields. The description echoes the tail parameter's semantics but adds no syntax or format detail beyond the schema, which is the expected baseline of 3 when the schema does the heavy lifting.

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?

States a specific verb and resource ('Read a task's log') and adds the paging behavior, so the agent knows exactly what it retrieves. It does not explicitly distinguish itself from the log-reading siblings (proxmox_get_ceph_log, proxmox_get_cluster_log), though the word 'task's' implicitly scopes it to a single task UPID.

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 only implied: an agent can infer it should call this when it has a task UPID and needs that task's output. There is no explicit when-to-use vs. when-not guidance and no mention of the natural alternative, proxmox_get_task (for status) or proxmox_wait_for_task (for completion).

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