Skip to main content
Glama
tiancode
by tiancode

pve_vm_clone

Clone a VM or container to a new, unused VM ID. Create a full independent copy or a linked clone from a template, with optional target storage and node placement.

Instructions

Clone a VM or container to a new vmid.

    Applies to: QEMU VMs and LXC containers, located by ``vmid`` (``node``
    optional and auto-resolved). ``newid`` must be unused. ``full=true``
    makes an independent full copy (required when the source is not a
    template); linked clones (``full=false``) need a template source.
    ``storage`` sets the target storage for a full clone; ``target_node``
    places the clone on another node (shared storage required).

    Side effects: creates a new guest (stopped). Clones often outlast the
    PVE_MCP_TASK_WAIT window — then ``task.status`` is "running" and the
    ``upid`` can be followed with pve_task_status. Returns JSON with
    ``vmid`` (source), ``newid``, ``node``/``type`` and ``task``.
    Source: POST /nodes/{node}/{qemu|lxc}/{vmid}/clone.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fullNo
nameNo
nodeNo
vmidYes
newidYes
storageNo
target_nodeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Discloses side effects: creates a stopped guest, asynchronous task behavior, and return structure. No annotations exist, so the description fully shoulders the burden of behavioral transparency.

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?

Well-structured with paragraphs and bullet points. Every sentence adds value, no fluff. Front-loaded with main action.

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?

Covers all aspects: operation, parameters, side effects, async handling, and return fields. Despite presence of an output schema, the description still provides necessary context.

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?

Adds meaning beyond schema for key parameters: newid must be unused, full makes independent copy, storage sets target for full clone, target_node requires shared storage. Missing explanation for 'name' and 'node', but overall compensates for 0% schema coverage.

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?

Clearly states 'Clone a VM or container to a new vmid.' Uses specific verb and resource, and distinguishes from sibling tools like migration or backup.

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?

Explicitly explains when to use full vs linked clones, requirements (template for linked, full for non-template), and options like storage and target_node. Provides clear context for appropriate usage.

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/tiancode/pve-mcp'

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