Skip to main content
Glama

xo_migrate_vm

Live-migrate an XCP-ng VM to another host by specifying the VM ID and target host ID, keeping workloads running during host moves.

Instructions

Live-migrate an XCP-ng VM to another host.

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": {
      "vm_id": "<vm_id>",
      "target_host_id": "<target_host_id>"
    },
    "name": "xo_migrate_vm"
  }
}

Input Schema

NameRequiredDescriptionDefault
vm_idYes
gateway_idNo
target_host_idYes

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?

No annotations are supplied, so the description carries the full behavioral burden. It discloses that the migration is live (the guest stays running), but says nothing about downtime characteristics, whether the VM must reside on shared storage, required permissions, or what happens on failure for this long-running operation.

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?

A single front-loaded sentence with no filler. It is efficient, though its brevity reflects under-specification rather than disciplined conciseness.

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 mutating, potentially long-running infrastructure operation with zero annotations, no output schema, and undocumented parameters, one sentence is not enough. An agent has no basis to decide preconditions, interpret gateway_id, or anticipate failure behavior.

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 three parameters. The description only loosely implies target_host_id ('to another host'); vm_id is obvious from the name, but gateway_id is completely unexplained in both schema and description, which is a meaningful gap for an optional connectivity parameter.

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 VM) plus the platform (XCP-ng), which distinguishes it from the Proxmox and vSphere migrate siblings. It stops short of naming the source/target scope explicitly, but the action is unambiguous.

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 mention of prerequisites such as shared storage, pool membership, or host compatibility, and no differentiation from xo_v2v_migrate. The only hint is that migration is 'live', leaving the agent to infer everything else.

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