Skip to main content
Glama

vsphere_migrate_vm

Live-migrate a vSphere VM to another ESXi host using vMotion. Set dry_run to true to validate the move without relocating the VM.

Instructions

Live-migrate (vMotion) a vSphere VM to another ESXi host. Set dry_run=True to validate without moving.

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": {
      "name": "<name>",
      "target_host": "<target_host>"
    },
    "name": "vsphere_migrate_vm"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
dry_runNo
gateway_idNo
target_hostYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden and does disclose two useful traits: the migration is live (vMotion) and dry_run validates without moving the VM. It says nothing about required permissions, cluster/host compatibility prerequisites, whether the call blocks until completion, or failure behavior — significant omissions for a live-migration mutation.

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?

Two short sentences with zero filler; the core action is front-loaded and the safety switch follows immediately. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter mutation with no annotations and no output schema, the description covers the essential action and the dry-run escape hatch, which is the minimum an agent needs to call it safely. It falls short on prerequisites, permissions, the unexplained gateway_id, and any indication of what a successful migration returns.

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 description coverage is 0% across four parameters, so the description must compensate; it does explain 'name' (the VM), 'target_host' (another ESXi host), and the meaning and effect of 'dry_run' precisely. Only 'gateway_id' is left completely unexplained, which is a meaningful but limited gap.

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 description pairs a specific verb ('Live-migrate (vMotion)') with a specific resource and destination ('a vSphere VM to another ESXi host'), so the agent knows exactly what operation this performs. It does not explicitly differentiate itself from the sibling migrate tools (proxmox_migrate_vm, xo_migrate_vm), though the vSphere/ESXi framing makes the platform unambiguous.

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?

The only usage guidance is parameter-level: 'Set dry_run=True to validate without moving,' which tells the agent how to do a safe trial run. There is no statement of when to choose this over the sibling migration tools, nor any prerequisites or exclusions.

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