Nutanix AIops

vm_migrate

Destructive

Live-migrate a Nutanix VM to another host, preview the move with dry_run, and revert to the original host if needed.

Instructions

[WRITE][risk=high] Live-migrate a VM to another host (reversible → prior host).

Pass dry_run=True to preview. Tagged risk=high (audit tier 'review');
NUTANIX_AUDIT_APPROVED_BY / NUTANIX_AUDIT_RATIONALE optionally annotate
who/why.

Args:
    vm_ext_id: VM extId as returned by vm_list.
    target_host_ext_id: Destination host extId (from host_list).
    dry_run: If True, preview the migration without performing it.
    target: Prism Central target name from config; omit for the default.

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_ext_id": "<vm_ext_id>",
      "target_host_ext_id": "<target_host_ext_id>"
    },
    "name": "vm_migrate"
  }
}

Input Schema

Name	Required	Description	Default
`target`	No
`dry_run`	No
`vm_ext_id`	Yes
`target_host_ext_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 28, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Goes beyond the annotations by disclosing live migration, reversibility back to the prior host, risk=high audit tier 'review', and optional approval/rationale env vars. It doesn't state what happens on failure or partial migration, but the risk and audit context is richer than the raw hints.

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?

Front-loads the [WRITE][risk=high] tags and one-line purpose, then a compact Args block. Efficient overall, though the audit/approval sentence is slightly run-on and the tag prefixes duplicate the annotation hints.

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 mutating tool with no output schema, it covers risk, reversibility, preview, and every parameter. Only failure semantics and post-migration state are unaddressed, which is a minor gap given how much is otherwise specified.

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?

Despite 0% schema description coverage, the description documents all four params and their provenance (vm_ext_id from vm_list, target_host_ext_id from host_list, dry_run preview behavior, target config default). This meaningfully compensates for the empty schema, though formats are still terse.

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?

States a specific verb and resource (live-migrate a VM) plus the destination (another host), which cleanly distinguishes it from sibling write operations like vm_clone, vm_protect, and vm_power_on. An agent can identify the operation without opening the schema.

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?

Implies usage context ('Live-migrate', use dry_run=True to preview) but never states when to choose this over alternatives such as vm_protect or cluster-level rebalancing, nor any prerequisites for the source/target hosts. The dry_run preview hint is the only actionable guidance.

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