Skip to main content
Glama

Migrate all VMs/CTs off node

node_migrate_all

Migrate all VMs and containers off a node to other nodes, with live migration and auto-distribution. Optionally set a specific target node.

Instructions

Bulk-migrate all VMs/containers off this node to others (live).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeYes
targetNoSpecific target node (else auto-distribute)
max_workersNo
with_local_disksNo
Behavior2/5

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

The description adds only 'live' migration, which is minimal behavioral context. It does not address what happens if some migrations fail, whether migration is sequential or parallel, or any requirements like target node availability. Given no annotations cover these details, the description is insufficient.

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?

The description is concise with a single sentence that starts with the verb 'Bulk-migrate'. However, it sacrifices necessary detail for brevity, making it less helpful than it could be.

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

Completeness1/5

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

For a complex bulk migration tool with 4 parameters and no output schema, the description is inadequate. It does not cover behavior, parameter meanings, error conditions, or required preconditions, leaving the agent with insufficient information to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 25% schema coverage, the description should compensate by explaining parameters, but it does not mention any parameters. It vaguely implies the node parameter as source and 'to others' hints at distribution but fails to detail target, max_workers, or with_local_disks.

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 clearly states the action (bulk-migrate), resource (all VMs/containers off this node), and method (live). It effectively distinguishes from sibling tools like migrate_vm or migrate_container which handle single migrations.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like migrate_vm or migrate_container. It does not mention prerequisites, potential risks, or scenarios where this tool should be avoided.

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/ngocdd/proxmox-mcps'

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