Skip to main content
Glama
claude-proxmox-controller

claude-proxmox-controller

create_vm

Create a Proxmox VE virtual machine that boots an ISO and automate Linux or Windows installs with profiles, user setup, and optional start.

Instructions

Create a VM that boots an ISO image (see list_install_media). Profiles: linux, win11 (UEFI, Secure Boot, TPM 2.0), win10, other. It gets a SPICE display, sound and a USB tablet. Windows (win11/win10) installs itself with windows_user: the app puts an answer file on a disc of its own — VirtIO drivers from virtio_iso, the edition, no setup questions, that user with a password the USER types in Proxmox Controller's window (you never give or see it), optionally Remote Desktop and the dark theme, and the VirtIO guest tools with the QEMU guest agent last; with start, the app presses Enter at the installer's 'Press any key to boot from CD' itself (it waits only seconds). The disc is deleted once Windows is ready. An Ubuntu Server ISO from 24.04 on (profile linux) installs itself with linux_user: autoinstall answers on a disc of the app's — that user with the password the USER types, optionally an SSH key and a static_ip, the whole disk, the QEMU guest agent, OpenSSH, the host's time zone; with start, the app types yes at the installer's 'Continue with autoinstall?' itself. About 15 minutes; the disc is deleted once the agent answers.

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

Input Schema

NameRequiredDescriptionDefault
isoYesAn ISO's volid.
hostYesThe host's id, from list_hosts.
nameYes
nodeNo
vmidNo
coresNo
startNo
bridgeNo
reasonYesWhy you are doing this, in a sentence. The user sees it in the approval window and in the log.
disk_gbNo
editionNoAs the installer lists it. Default: Windows 11 Pro (win10: Windows 10 Pro). Remote Desktop needs Pro, Education, Enterprise or Server.
profileNo
storageNo
host_cpuNo
languageNoSuch as en-US or el-GR. Default: from the ISO's name, else en-US. The keyboard is English (US).
static_ipNoWith linux_user: a fixed address such as 192.168.1.50; the network's size, gateway and DNS are the host's own (on the VM's bridge). Default: DHCP.
dark_themeNo
linux_userNoAn Ubuntu Server ISO installs itself with this user (sudo); the user types its password.
memory_mibNo
virtio_isoNo
guest_agentNo
windows_userNoWindows installs itself with this user (an administrator); the user types its password.
start_at_bootNo
remote_desktopNo
ssh_public_keyNoWith linux_user.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior5/5

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

With annotations only declaring readOnlyHint=false and destructiveHint=false, the description carries and richly delivers the behavioral burden: it discloses that install takes about 15 minutes, that the app injects an answer file on its own disc, that the password is typed by the user in the Proxmox Controller window and never seen by the agent, that the installer prompt is handled automatically with start, and that the auxiliary disc is deleted once the install finishes. These are exactly the side effects and async traits an agent needs and cannot get from the annotations.

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?

The lead sentence is well front-loaded, but what follows is two very long em-dash-chained sentences written as run-on prose, making the Windows and Linux paths hard to scan. The content is substantive rather than filler, yet it would be far more usable split into parallel bullets for the two install profiles.

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 25-parameter, non-idempotent creation tool with no output schema and no return-value contract, the description covers the important operational unknowns: install duration, automation of installer prompts, credential handling, and disc lifecycle. The remaining gap is that a third of the parameters – sizing, storage, node/vmid placement, bridge – receive no semantic explanation anywhere.

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 only 36% across 25 parameters, so the description must compensate, and it does add meaning for a cluster of them: windows_user (administrator account), linux_user (sudo user), virtio_iso, ssh_public_key, static_ip, dark_theme, remote_desktop, guest_agent and start. It says nothing about node, vmid, cores, memory_mib, disk_gb, storage, bridge, host_cpu, or start_at_boot, which remain documented only by name and type, so it partially but not fully closes the 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?

Opens with a specific verb and resource ('Create a VM that boots an ISO image') and immediately routes to list_install_media for the ISO identifier, so the agent knows this is an ISO-boot VM builder. It does not explicitly differentiate itself from create_cloud_vm or clone_vm, which is why it falls short of a 5.

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 through the profile enumeration (linux, win11, win10, other) and the conditional pairing of linux_user with Ubuntu Server ISOs and windows_user with win11/win10, which effectively tells the agent which profile/user combination to pick. However, there is no explicit when-not guidance and no mention of when to prefer create_cloud_vm or clone_vm instead, leaving the main selection decision to inference.

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