Skip to main content
Glama
Sign In
homebutler

homebutler

by Higangssh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

proxmox_tasks

Read-only

Retrieve the 50 most recent Proxmox tasks for a node to monitor activity and diagnose task status.

Instructions

Get the 50 most recent Proxmox tasks for a node

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": {
      "node": "<node>"
    },
    "name": "proxmox_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeYesProxmox node name
endpointNoProxmox endpoint name from config (optional when exactly one is configured)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.22.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the useful 50-result cap and node scoping, but says nothing about ordering guarantees, task states returned, or whether results can be paged beyond 50.

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 front-loaded sentence with no waste; the result cap and node scoping are both conveyed efficiently.

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?

For a read-only listing tool with fully documented parameters and no output schema, the description covers the essential scope and result limit. It could note what a task record contains or whether status filtering is possible, but nothing critical for a correct call is missing.

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 both node and endpoint are already documented in the schema. The description adds no format details or constraints for either parameter, so baseline 3 is appropriate.

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 (Get) and resource (Proxmox tasks) with explicit scope: 50 most recent, filtered by node. It is distinguishable from the sibling proxmox_task_status by name, though the description does not explicitly contrast the two.

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 — list recent tasks for a node — but there is no explicit guidance on when to prefer this over proxmox_task_status or proxmox_status for individual task details or broader node status. The agent must infer the boundary from tool names alone.

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