Skip to main content
Glama
claude-proxmox-controller

claude-proxmox-controller

download_iso

Instruct a Proxmox host to download an ISO image from a URL for VM or container installation, with optional node, storage, filename, and SHA-256 checksum.

Instructions

Have the host download an ISO image from a web address.

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>",
      "url": "<url>",
      "reason": "<reason>"
    },
    "name": "download_iso"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
hostYesThe host's id, from list_hosts.
nodeNo
reasonYesWhy you are doing this, in a sentence. The user sees it in the approval window and in the log.
storageNo
filenameNo
checksum_sha256No

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the mutation profile is covered. The description adds essentially nothing beyond that: it does not say where the ISO lands on the host, whether the download is re-runnable or overwrites an existing file, or that a user approval is triggered (a detail only hinted at by the 'reason' schema field).

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?

A single front-loaded sentence with no filler or redundancy. It is concise, though the brevity edges into under-specification rather than tight economy.

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 7-parameter mutation tool with low schema coverage and no output schema, a one-sentence description is thin. However, the annotations do carry the safety profile and the schema at least documents host and reason, so the description is not wholly insufficient—just minimal relative to the tool's complexity.

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?

Schema description coverage is only 29% across 7 parameters, so the description carries a heavy burden here. It only implicitly maps to 'url' via 'from a web address' and says nothing about node, storage, filename, or checksum_sha256, leaving five parameters undocumented in either place.

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 sentence states a specific verb ('download') and resource ('ISO image') and clarifies the agent of the action ('Have the host'). That is enough to distinguish it from VM-creation siblings like create_vm or create_cloud_vm, though it never names an alternative explicitly.

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 guidance on when this tool should be chosen over alternatives such as create_vm or get_cloud_image, no prerequisites (e.g. a reachable host, approval flow), and no exclusions. The agent must infer the use case entirely from the tool name and description.

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