Skip to main content
Glama
tiancode
by tiancode

pve_vm_migrate

Migrate a VM or container to another Proxmox node, with live migration for running QEMU VMs and restart migration for LXC containers.

Instructions

Migrate a VM or container to another node.

    Applies to: QEMU VMs and LXC containers, located by ``vmid`` (source
    ``node`` optional and auto-resolved). For a running QEMU VM pass
    ``online=true`` for live migration. LXC containers cannot live-migrate:
    for them ``online=true`` is mapped to PVE restart migration (the CT is
    stopped, migrated, and started on ``target_node``).

    Side effects: moves the guest (brief downtime for CT restart migration).
    Waits up to PVE_MCP_TASK_WAIT seconds for the PVE task; returns JSON with
    ``vmid``/``node`` (source)/``target_node``/``type`` and ``task``
    (``exitstatus`` "OK", failure + ``log_tail``, or ``status`` "running"
    with the ``upid`` to follow up via pve_task_status — migrations often
    outlast the wait window).
    Source: POST /nodes/{node}/{qemu|lxc}/{vmid}/migrate.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNo
vmidYes
onlineNo
target_nodeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, the description fully discloses side effects (moves guest, brief downtime for CT), the waiting behavior (up to PVE_MCP_TASK_WAIT seconds), and the return JSON structure with exitstatus, failure details, and status running with upid. This is comprehensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is comprehensive but somewhat lengthy. It front-loads the main purpose and each sentence adds value. Slightly more conciseness could improve, but it remains well-structured and informative.

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?

The tool has 4 parameters, 2 required, and an output schema (implied by context). The description covers migration behavior, parameter details, side effects, and return values. It provides sufficient context for an agent to use the tool correctly.

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 0%, so the description must compensate. It explains vmid, target_node, and online, but does not explicitly describe the 'node' parameter (only mentions it is optional and auto-resolved). The description adds meaning to most parameters but lacks explicit detail for one, resulting in partial compensation.

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 action (Migrate) and the resource (VM or container). It distinguishes between QEMU VMs and LXC containers, and specifies the behavior for each. No sibling tool performs migration, so differentiation is not needed.

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?

The description explains when to use online=true for live migration (running QEMU VM) and when it maps to restart migration (LXC containers). It also notes that the source node is optional and auto-resolved. It does not explicitly state when not to use the tool, but the context is clear.

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