Skip to main content
Glama

Check container migration preconditions

proxmox_check_container_migration
Read-only

Checks whether an LXC container can migrate and identifies allowed target nodes, reporting running state and local disks or mounts that block migration. Call before migrating.

Instructions

Check whether an LXC container can be migrated, and to which nodes: reports running state, local disks/mount points that block migration, and allowed/not-allowed target nodes. Call before proxmox_migrate_container.

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_container_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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.2/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 adds real value by disclosing what the check surfaces (running state, blocking mounts, per-node eligibility). It stops short of saying whether partial results are returned or how the allowed/not-allowed lists are structured, which matters slightly since there is no output schema.

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 sentences, zero filler, with the core question ('can this container be migrated') front-loaded and the precondition call instruction trailing in the natural reading position.

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 necessary work of listing the three result categories an agent should expect. It is complete enough to call correctly; only the exact shape of the allowed/not-allowed node lists remains unstated, a minor gap for a read-only precheck.

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%, and the schema already explains that node is auto-resolved from vmid and that target is the node to check. The description adds only the loose phrase 'to which nodes,' which maps to target but gives no extra syntax or semantics. Baseline 3 applies when the schema carries the parameter burden.

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?

The description gives a specific verb (Check) plus resource (LXC container migration) and then enumerates exactly what is reported: running state, blocking local disks/mount points, and allowed/not-allowed target nodes. The 'LXC container' scoping also separates it from the sibling proxmox_check_vm_migration without needing to name it.

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?

It states a clear usage context: 'Call before proxmox_migrate_container,' which establishes the sequencing relationship to the migration tool. It does not include any when-not guidance or point to proxmox_check_vm_migration for VMs, so it stops short of full alternative routing.

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