Skip to main content
Glama
phantosmax

CloudStack MCP Server

by phantosmax

start_virtual_machine

Use this tool to initiate the startup of a virtual machine by specifying its unique VM ID, enabling resource activation within the CloudStack MCP Server environment.

Instructions

Start a virtual machine

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesVM ID to start

Implementation Reference

  • The main handler function that executes the start_virtual_machine tool logic. It calls the CloudStack client to start the VM and returns a formatted response with the job ID.
    async handleStartVirtualMachine(args: any) {
      const result = await this.cloudStackClient.startVirtualMachine({ id: args.id });
      
      return {
        content: [
          {
            type: 'text',
            text: `Started virtual machine ${args.id}. Job ID: ${result.startvirtualmachineresponse?.jobid}`
          }
        ]
      };
    }
  • The tool definition including name, description, and input schema that requires a 'id' parameter.
    {
      name: 'start_virtual_machine',
      description: 'Start a virtual machine',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'string',
            description: 'VM ID to start',
          },
        },
        required: ['id'],
        additionalProperties: false,
      },
    },
  • src/server.ts:112-113 (registration)
    Tool registration in the MCP server's CallToolRequest handler switch statement, which dispatches to the VirtualMachineHandlers.handleStartVirtualMachine method.
    case 'start_virtual_machine':
      return await this.vmHandlers.handleStartVirtualMachine(args);
  • Helper method in CloudStackClient that performs the actual API request to CloudStack's startVirtualMachine endpoint.
    async startVirtualMachine(params: CloudStackParams): Promise<CloudStackResponse> {
      return this.request('startVirtualMachine', params);
    }
Behavior2/5

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

With no annotations, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits like whether this requires admin permissions, if it's asynchronous, potential side effects, or what happens on failure. This leaves significant gaps for a mutation tool.

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, direct sentence with zero wasted words. It's front-loaded with the core action, making it highly efficient and easy to parse.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on permissions, side effects, error handling, or return values, leaving the agent with insufficient context to use it safely and effectively.

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%, so the parameter 'id' is documented in the schema as 'VM ID to start'. The description adds no additional meaning beyond this, such as format examples or constraints, meeting the baseline for high schema coverage.

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 ('Start') and resource ('a virtual machine'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'reboot_virtual_machine' or 'stop_virtual_machine', which prevents a perfect score.

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 like 'reboot_virtual_machine' or 'deploy_virtual_machine'. The description lacks context about prerequisites (e.g., VM must be stopped) or exclusions, offering minimal usage direction.

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