Skip to main content
Glama
claude-proxmox-controller

claude-proxmox-controller

get_cloud_image

Downloads an official supported Ubuntu Server LTS cloud image to a Proxmox host once, so you can create VMs from it with create_cloud_vm.

Instructions

Have the host download Ubuntu Server's official cloud image — an LTS release still supported (list_install_media: cloud_images_offered) — once, to make VMs from with create_cloud_vm.

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

Input Schema

NameRequiredDescriptionDefault
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.
releaseNoSuch as 24.04 or 26.04; a new LTS shows in list_install_media by itself.
storageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world operation; the description adds that the download occurs on the host and that only supported LTS releases qualify. It does not disclose image size, transfer time, or whether a repeat call re-downloads, which matters given idempotentHint=false. The 'once' advice is useful behavioral context beyond the annotations but not deep.

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?

A single sentence with the action front-loaded, but it is clause-heavy with a parenthetical and awkward phrasing ('make VMs from with create_cloud_vm'), which slightly hurts readability. Every element is relevant; the execution is just clumsy.

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 5-parameter host-mutating tool with no output schema, the description covers the workflow and release gating but omits what 'node' and 'storage' do and gives no sense of what the call returns or how long it takes. An agent can call it, but must open the schema for a full picture.

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 coverage is 60%, with 'host' and 'reason' well documented in the schema itself. The description only touches 'release' indirectly ('an LTS release still supported') and says nothing about 'node' or 'storage', the two undocumented parameters. Baseline 3 is appropriate but the description does not compensate for the coverage gap.

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: download Ubuntu Server's official LTS cloud image to a host. It also names the downstream tool ('create_cloud_vm') and the discovery tool ('list_install_media'), so an agent can place it in the provisioning workflow. It does not contrast itself with the sibling 'download_iso', leaving the cloud-image-vs-ISO distinction implicit.

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

Usage Guidelines4/5

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

Gives clear when-to-use context: download once, in order to build VMs with create_cloud_vm, and points to list_install_media for release discovery. The 'once' framing tells the agent not to loop this call. No explicit when-not guidance (e.g., use download_iso for non-cloud images) is provided.

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