Skip to main content
Glama

xo_v2v_migrate

Migrate VMware ESXi VMs to XCP-ng with warm V2V migration: stream disks while the source VM runs, then cut over briefly to limit downtime.

Instructions

Migrate a VM from VMware ESXi to XCP-ng using V2V warm migration.

Warm migration streams disk data while the source VM is still running, then performs a brief cutover (seconds of downtime). Works with all ESXi versions including VMFS6 and VSAN.

Write operation — recorded in the audit log.

Args: esxi_id: Source ESXi server ID. vm_name: Name of the VM to migrate on ESXi. target_sr: Target storage repository UUID on XCP-ng (optional). target_network: Target network UUID on XCP-ng (optional). gateway_id: Target gateway (optional).

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": {
      "esxi_id": "<esxi_id>",
      "vm_name": "<vm_name>"
    },
    "name": "xo_v2v_migrate"
  }
}

Input Schema

NameRequiredDescriptionDefault
esxi_idYes
vm_nameYes
target_srNo
gateway_idNo
target_networkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add real behavioral value: it discloses that this is a warm migration with only seconds of downtime, that disk data streams while the source VM runs, and that the operation is written to the audit log. It is silent on critical behaviors: what happens to the source VM afterward (stopped, left running, deleted), whether a partial failure is recoverable, what permissions/credentials are needed, and whether concurrent migrations are allowed.

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 front-loaded with the action and mechanism, then the compatibility note and audit flag, then args. The Args block largely duplicates the schema property names, which is somewhat redundant, but each sentence otherwise earns its place and the total length is appropriate for a mutation tool.

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?

For a five-parameter write operation with no annotations and no output schema, the definition covers purpose, mechanism, downtime profile, compatibility, auditability, and all parameter roles. The remaining gap is what the call returns and how to track the migration's progress afterward, but the core information needed to invoke it correctly is present.

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 description coverage is 0%, so the description must compensate, and it does partially: it restates all five parameters and adds the key semantics that target_sr and target_network are UUIDs and that they live on the XCP-ng side, and flags three params as optional. It does not explain selection rules when optional params are omitted (e.g., which SR or network is chosen by default) or any format constraints beyond 'UUID'/'name'.

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?

The first sentence names a specific verb and resource pair — migrating a VM from VMware ESXi to XCP-ng via V2V warm migration — and the following sentences explain the mechanism (streaming disk data while the source runs, brief cutover). An agent can tell this apart from generic migration siblings like xo_migrate_vm or proxmox_migrate_vm by the explicit ESXi→XCP-ng direction. It stops short of naming an alternative tool as a contrast, so it is not a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied: it is a warm migration applicable to 'all ESXi versions including VMFS6 and VSAN', which tells the agent which environments this fits. However, there is no explicit when-to-use versus when-not guidance, no prerequisites (e.g., that esxi_id must come from an ESXi listing tool, that the XCP-ng pool must already exist), and no mention of when a cold migration or other sibling would be preferable.

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