Skip to main content
Glama

proxmox_migrate_vm

Live-migrate a running Proxmox VM from one node to another, keeping the guest online during the move.

Instructions

Live-migrate a Proxmox VM to another node.

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": {
      "vmid": "<vmid>",
      "node": "<node>",
      "target": "<target>"
    },
    "name": "proxmox_migrate_vm"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeYes
vmidYes
onlineNo
targetYes
gateway_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and mostly fails it: it does not say whether the call blocks until migration completes, whether the VM keeps running (only the word 'Live' hints at it), what happens to the source-side VM on failure, or whether required permissions exist. For a destructive-capable mutation on a hypervisor this is a significant gap.

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?

One short sentence, front-loaded with the verb and scope, with no filler. It is efficient rather than verbose; the problem is underspecification, not wordiness.

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 5-parameter, no-annotation, mutation tool with no output schema, the description is far too thin. An agent would need to guess at migration mode semantics, prerequisite cluster state, and blocking behavior before calling it safely.

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 description coverage is 0% across 5 parameters, and the description only implicitly covers vmid and target. It says nothing about 'node' (presumably the source node), 'online' (which contradicts or at least overlaps with 'live-migrate'), or 'gateway_id', leaving three parameters undocumented in both places.

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?

States a specific verb and resource ('Live-migrate a Proxmox VM to another node'), and the Proxmox qualifier separates it from the sibling vsphere_migrate_vm and xo_migrate_vm tools. It does not, however, clarify the distinction between the live and offline modes that the 'online' parameter exposes.

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 when-to-use guidance, no prerequisites (cluster membership, shared storage, quorum), and no mention of when an offline migration or a start/stop pair would be preferable. The agent must infer all routing decisions from the name alone.

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

Deploy Server

Other Tools