Skip to main content
Glama

pdm_pve_qemu_migrate

Migrate a QEMU VM to a different node within a Proxmox cluster using PDM. Supports live migration (online) and dry-run planning before submission.

Instructions

MUTATION: migrate a VM to another node within the remote's cluster (through PDM).

For a container use pdm_pve_lxc_migrate; for a different remote/datacenter use pdm_pve_qemu_remote_migrate; to drive a cluster directly without PDM use pve_guest_migrate. online=True migrates it running; the default requires it stopped first. Dry-run by default (PLAN); confirm=True submits and returns a PDM task reference — track it with pdm_tasks_list (pve_task_status cannot poll a PDM UPID).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vmidYesNumeric VMID of the VM to migrate, as a string.
onlineNoTrue live-migrates the VM; else it must be stopped.
remoteYesPDM-registered remote (Proxmox cluster) currently hosting the VM.
targetYesDestination node name within the same remote's cluster.
confirmNoFalse (default) returns a PLAN only; True submits it.
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 the mutation nature, the online flag requirement, dry-run default, confirm behavior, and tracking limitations. It does not cover all possible side effects but adequately informs the agent of key behaviors.

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?

Five sentences, each providing essential information without redundancy. Front-loaded with the action and MUTATION tag. Every sentence earns its place, covering purpose, alternatives, parameters, and tracking.

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?

Given 6 params, 100% schema coverage, output schema, and detailed description, it covers core workflow, alternatives, state requirements, and tracking. Could mention prerequisites like shared storage but overall comprehensive.

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 coverage is 100% (baseline 3). Description adds meaning: explains 'online' flag semantics, 'confirm' flag dry-run vs submission, and tracking context for the returned reference. This adds significant value beyond the schema.

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?

Description clearly states the action: migrate a VM to another node within the same remote's cluster via PDM. It distinguishes from siblings by naming alternatives for containers (pdm_pve_lxc_migrate), different remote/datacenter (pdm_pve_qemu_remote_migrate), and direct cluster migration without PDM (pve_guest_migrate).

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 provides when-to-use and when-not-to-use guidance: 'For a container use pdm_pve_lxc_migrate; for a different remote/datacenter use pdm_pve_qemu_remote_migrate; to drive a cluster directly without PDM use pve_guest_migrate.' Also explains the online flag and dry-run behavior.

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