Skip to main content
Glama

pve_node_migrateall

Migrate all or filtered guests from a source node to a destination node in Proxmox. Dry-run returns a plan; confirm to submit the migration tasks.

Instructions

MUTATION: migrate all (or filtered) guests from a node to a target node.

RISK_HIGH, NOT auto-reversible: reversal requires a second pve_node_migrateall back, which may not restore the original state. target = destination node name (required). For a single guest instead of the whole node use pve_guest_migrate. Dry-run by default (returns a PLAN); confirm=True executes (POST, Smoke-confirm) and returns {"status": "submitted", "result": <task UPID | None>} — poll with pve_task_status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vmsNoOptional comma-separated list of VMIDs/CTIDs to limit the scope; omit to migrate all guests on the node.
nodeNoSource PVE node name whose guests to migrate; defaults to the configured node if omitted.
targetYesDestination PVE node name to migrate guests to.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the bulk migration.
maxworkersNoMaximum number of parallel migration workers to run.
proximo_targetNoWhich configured Proxmox target to run this call against — a target name from your multi-target config (a specific PVE/PBS/PMG/PDM box). Omit to use the single/default target from the environment; the selection applies only to this call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Describes mutation nature, risk level, dry-run default, execution confirmation, and output format (status with task UPID). As no annotations exist, the description fully covers behavioral traits.

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?

Well-structured: starts with purpose, then risk warning, parameter details, and usage guidance. Every sentence adds value; no fluff.

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

Completeness5/5

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

Covers purpose, usage, risk, parameters, dry-run vs execution, output structure, and polling mechanism. Output schema exists, but description still provides necessary context for safe operation.

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?

Adds context beyond the input schema: target required, vms for filtering, node defaults to configured node, confirm=False for dry-run, and proximo_target for multi-target setups. Schema coverage is 100%, but description enhances understanding.

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?

Clearly states it migrates all or filtered guests from a source node to a target node. Distinguishes from pve_guest_migrate for single guest migration.

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

Usage Guidelines5/5

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

Explicitly tells when to use this tool vs pve_guest_migrate for single guests. Explains default dry-run behavior and confirms execution with confirm=True. Also notes high risk and non-auto-reversibility.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/john-broadway/proximo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server