Skip to main content
Glama
phantosmax

CloudStack MCP Server

by phantosmax

migrate_virtual_machine

Migrate virtual machines to a specified host using VM and host IDs to optimize resource allocation and manage CloudStack infrastructure efficiently.

Instructions

Migrate virtual machine to another host

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostidNoTarget host ID
virtualmachineidYesVM ID to migrate

Implementation Reference

  • The main handler function that executes the migrate_virtual_machine tool. It calls the CloudStack client to migrate the VM and returns a success message with the job ID.
    async handleMigrateVirtualMachine(args: any) {
      const result = await this.cloudStackClient.migrateVirtualMachine(args);
      
      return {
        content: [
          {
            type: 'text',
            text: `Migrated virtual machine ${args.id}. Job ID: ${result.migratevirtualmachineresponse?.jobid}`
          }
        ]
      };
    }
  • The tool definition including name, description, and input schema (requires virtualmachineid, optional hostid).
      name: 'migrate_virtual_machine',
      description: 'Migrate virtual machine to another host',
      inputSchema: {
        type: 'object',
        properties: {
          virtualmachineid: {
            type: 'string',
            description: 'VM ID to migrate',
          },
          hostid: {
            type: 'string',
            description: 'Target host ID',
          },
        },
        required: ['virtualmachineid'],
        additionalProperties: false,
      },
    },
  • src/server.ts:124-125 (registration)
    MCP server registration/dispatch: switch case that routes the tool call to the VM handler.
    case 'migrate_virtual_machine':
      return await this.vmHandlers.handleMigrateVirtualMachine(args);
  • CloudStack client helper method that makes the actual API request to migrateVirtualMachine.
    async migrateVirtualMachine(params: CloudStackParams): Promise<CloudStackResponse> {
      return this.request('migrateVirtualMachine', params);
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose critical behavioral traits such as whether the migration is live or requires downtime, permission requirements, potential impacts on VM state, or any rate limits. This leaves significant gaps for an agent to understand the operation's implications.

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?

The description is a single, clear sentence with zero wasted words. It's front-loaded with the core action and efficiently communicates the essential purpose without unnecessary elaboration, making it easy for an agent to parse quickly.

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

Completeness2/5

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

Given the complexity of a VM migration operation, no annotations, and no output schema, the description is insufficient. It lacks details on behavioral aspects, error conditions, return values, or integration with sibling tools like 'list_hosts'. For a potentially disruptive operation, more context is needed to guide safe and effective use.

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 description coverage is 100%, with clear parameter descriptions in the schema itself. The tool description adds no additional parameter semantics beyond implying migration involves a source VM and target host. Since the schema already documents both parameters well, the baseline score of 3 is appropriate as the description doesn't enhance or contradict the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('migrate') and resource ('virtual machine'), specifying the destination ('to another host'). It distinguishes from siblings like 'deploy_virtual_machine' or 'scale_virtual_machine' by focusing on migration rather than creation or resizing. However, it doesn't explicitly differentiate from all similar operations like 'change_service_offering_virtual_machine' which might involve host changes.

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 guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., VM must be stopped), constraints (e.g., compatible hosts), or suggest other tools for related tasks like 'list_hosts' for host selection. The description is purely functional without contextual usage advice.

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

Related 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/phantosmax/cloudstack-mcp-server'

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