Skip to main content
Glama
phantosmax

CloudStack MCP Server

by phantosmax

reboot_virtual_machine

Restart a virtual machine on the CloudStack MCP Server by specifying its VM ID, ensuring operational stability and resource efficiency in cloud infrastructure management.

Instructions

Reboot a virtual machine

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesVM ID to reboot

Implementation Reference

  • The main handler function that calls the CloudStack client to reboot the VM and returns a formatted response with the job ID.
    async handleRebootVirtualMachine(args: any) {
      const result = await this.cloudStackClient.rebootVirtualMachine({ id: args.id });
      
      return {
        content: [
          {
            type: 'text',
            text: `Rebooted virtual machine ${args.id}. Job ID: ${result.rebootvirtualmachineresponse?.jobid}`
          }
        ]
      };
    }
  • The tool definition including name, description, and input schema requiring a VM ID.
    {
      name: 'reboot_virtual_machine',
      description: 'Reboot a virtual machine',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'string',
            description: 'VM ID to reboot',
          },
        },
        required: ['id'],
        additionalProperties: false,
      },
    },
    {
  • src/server.ts:116-117 (registration)
    The switch case in the MCP server that registers and routes calls to the reboot handler.
    case 'reboot_virtual_machine':
      return await this.vmHandlers.handleRebootVirtualMachine(args);
  • The CloudStack client method that sends the actual API request to reboot the virtual machine.
    async rebootVirtualMachine(params: CloudStackParams): Promise<CloudStackResponse> {
      return this.request('rebootVirtualMachine', params);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Reboot' implies a destructive operation that will interrupt VM services, but the description doesn't specify whether this requires specific permissions, if it's reversible, what happens to running processes, or any rate limits. This is a significant gap 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 extremely concise at just four words, front-loading the essential information with zero wasted language. Every word earns its place by clearly communicating the core function.

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 destructive operation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what 'reboot' entails behaviorally, what the expected outcome is, or any constraints. Given the complexity of VM management and the lack of structured data, more context is needed.

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?

The schema description coverage is 100%, with the single parameter 'id' clearly documented as 'VM ID to reboot'. The description doesn't add any additional meaning beyond what's in the schema, but since the schema is complete, the baseline score of 3 is appropriate.

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 ('reboot') and target resource ('virtual machine'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'stop_virtual_machine' or 'reset_password_virtual_machine' that also operate on virtual machines, so it's not fully distinctive.

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 'stop_virtual_machine' or 'start_virtual_machine', nor does it mention prerequisites or context for rebooting. The description only states what it does, not when it should be used.

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