Skip to main content
Glama

Check VM migration preconditions

proxmox_check_vm_migration
Read-only

Check whether and where a VM can be migrated before starting migration, including allowed and blocked target nodes, local disks or devices, and mapped resources.

Instructions

Check whether and where a VM can be migrated before calling proxmox_migrate_vm: allowed and blocked target nodes (with unavailable storages or blocking HA rules), local disks that would need with_local_disks/targetstorage, local devices (PCI/USB passthrough) that block migration, and mapped resources.

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>"
    },
    "name": "proxmox_check_vm_migration"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeNoNode the guest is on. Looked up automatically from the VMID when omitted.
vmidYesVM or container ID (VMID), e.g. 100
targetNoTarget node to check specifically

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description then adds the substantive behavioral detail of what the check reports — allowed vs. blocked nodes with their blocking reasons (unavailable storage, HA rules), local disks, and PCI/USB passthrough devices. It does not mention that results are a point-in-time snapshot despite idempotentHint=false, which is the only notable omission.

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; the verb and the precondition framing come first, followed by the enumerated findings. The dense parenthetical list is information-rich but slightly hard to scan, keeping it just below the top mark.

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?

With no output schema, the description does the work of explaining what the caller will learn, which is the right call for a diagnostic tool. Remaining gaps are minor — freshness of results and explicit container-vs-VM routing are unaddressed.

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 coverage is 100%, with descriptions for vmid, node (auto-looked-up when omitted), and target, so the schema carries the parameter burden. The description only indirectly implies what the optional target node is for ('whether and where a VM can be migrated'), adding no syntax or format detail beyond the schema.

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?

Names a specific verb and resource (check VM migration preconditions) and scopes it clearly as a pre-flight for proxmox_migrate_vm. The enumeration of what is checked (target nodes, local disks, passthrough devices, mapped resources) makes it distinguishable from the container-migration sibling without reading either schema.

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

Usage Guidelines4/5

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

Explicitly states the sequencing rule: use this before calling proxmox_migrate_vm, and the mention of with_local_disks/targetstorage tells the agent which follow-up parameters the findings feed into. It does not state exclusions (for example, that containers need proxmox_check_container_migration), so it falls short of a full when/when-not specification.

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