Skip to main content
Glama
claude-proxmox-controller

claude-proxmox-controller

clone_vm

Copy a Proxmox VE VM or template to create a new VM, specifying its name, ID, storage, and full-clone options.

Instructions

Copy a VM or a template as a new 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>",
      "vmid": "<vmid>",
      "new_name": "<new_name>",
      "reason": "<reason>"
    },
    "name": "clone_vm"
  }
}

Input Schema

NameRequiredDescriptionDefault
fullNo
hostYesThe host's id, from list_hosts.
vmidYesThe guest's ID (VMID).
reasonYesWhy you are doing this, in a sentence. The user sees it in the approval window and in the log.
storageNo
new_nameYes
new_vmidNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/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 safety profile is covered. The description adds only the implicit point that the source is copied rather than moved; it says nothing about linked versus full clones (despite a 'full' parameter), ordering/approval behavior implied by the 'reason' parameter, or what happens on partial failure.

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 single sentence is front-loaded and free of waste, but its brevity crosses into under-specification for a seven-parameter mutation tool. Concise, yet it leaves the reader with nothing actionable beyond the name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter, non-idempotent write operation with no output schema and only 43% schema coverage, one sentence is not enough. Critical unknowns such as clone mode, storage target, and whether the source guest is affected are left entirely to the schema or to inference.

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 coverage is only 43%: host, vmid, and reason are documented, but new_name, new_vmid, storage, and full have no descriptions anywhere. The description provides no compensating meaning for those four parameters, leaving the agent to guess at clone mode and storage placement.

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 description states a specific verb ('Copy') and resource ('a VM or a template as a new VM'), which is enough to distinguish it from sibling creation tools like create_vm and create_cloud_vm, since it starts from an existing guest rather than from scratch. It does not explicitly name those siblings, so it stops 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 Guidelines2/5

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

There is no guidance on when to clone versus when to use create_vm/create_cloud_vm, no prerequisites (e.g., must the source be powered off?), and no mention of template-versus-VM behavior differences. The agent must infer all selection logic from the name and the schema.

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