Skip to main content
Glama

pve_clone

Clone a Proxmox guest to a new ID with options for full or linked clone. Dry-run by default to plan before execution; specify target storage for full clones.

Instructions

MUTATION: clone a guest to a new id. Dry-run by default; confirm=True. Async — returns a UPID (poll with pve_task_status). pool: place the new guest in a resource pool (needed when the token is pool-scoped). storage: target storage for the full clone's disks (full=True only) — keeps a clone off the source storage; refused for a linked clone (PVE only honors it on a full clone). To create a guest from scratch instead use pve_create_vm / pve_create_container.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fullNoIf true, make a full independent copy of the disks; if false (default), make a space-saving linked clone.
kindNoGuest type: `lxc` for a container or `qemu` for a VM.lxc
nameNoName to give the new cloned guest.
nodeNoPVE node the source guest runs on. Omit to resolve it automatically from the cluster.
poolNoResource pool to place the new guest in — needed when the calling token is pool-scoped.
vmidYesNumeric ID of the source guest to clone — VMID for a QEMU VM or CTID for an LXC container.
newidYesNumeric ID to assign to the new cloned guest.
confirmNoLeave `false` (default) to get a dry-run PLAN; set `true` to execute the clone.
storageNoTarget storage for the full clone's disks (full=True only); keeps the clone off the source storage. Refused for a linked clone.
proximo_targetNoWhich configured Proxmox target to run this call against — a target name from your multi-target config (a specific PVE/PBS/PMG/PDM box). Omit to use the single/default target from the environment; the selection applies only to this call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries full burden. It discloses mutation, dry-run default, async behavior returning UPID, and parameter constraints (pool needed for pool-scoped tokens, storage only for full clones). However, it omits potential side effects like guest downtime or error handling.

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?

The description is dense and efficient, front-loading the main purpose and async nature, then adding parameter guidance in a logical flow. Every sentence adds value with no redundancy.

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

Completeness5/5

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

Given the presence of an output schema, the description adequately covers return behavior (UPID polling), key parameter constraints, and alternative tools. It provides sufficient context for an agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers all parameters (100% coverage), but description adds valuable context beyond schema definitions, e.g., 'needed when the token is pool-scoped' for pool, and 'refused for a linked clone' for storage. This enriches agent understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('clone a guest to a new id') and distinguishes it from creating from scratch by referencing alternative tools pve_create_vm and pve_create_container. It also specifies the mutation nature and dry-run behavior.

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

Usage Guidelines5/5

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

The description explicitly provides when to use this tool versus alternatives, stating 'To create a guest from scratch instead use pve_create_vm / pve_create_container.' It also explains parameter usage contexts like pool and storage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/john-broadway/proximo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server