Skip to main content
Glama
soyrageagency

Proxmox MCP Server

Migrate guest

migrate_guest

Move virtual machines or containers between cluster nodes. Performs live migration for running guests to minimize downtime.

Instructions

Migrate a VM or container to another cluster node. Running guests are migrated online (live) when possible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guestYesVMID or name.
onlineNoForce online/offline (default: online if running).
targetYesTarget node name.
Behavior2/5

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

No annotations provided, and description only adds that running guests are migrated online when possible. Lacks details on destructive behavior (e.g., source removal), authorization needs, or failure modes.

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 concise sentences clearly convey the purpose and a key behavioral aspect. No unnecessary information.

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?

Adequately covers core functionality for a 3-parameter tool. Could mention preconditions or failure scenarios, but not essential for basic usage.

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?

Schema has 100% coverage with clear parameter descriptions. Description adds context about live migration behavior, complementing the online parameter's schema description.

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?

Description clearly states the action (migrate), resource (VM or container), and destination (another cluster node). It distinguishes from sibling tools like clone_guest or backup_guest by specifying migration to a node.

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?

No explicit guidance on when to use or not use this tool. No mention of prerequisites, alternatives, or when to prefer this over other migration methods.

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/soyrageagency/proxmox-mcp-server'

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