Skip to main content
Glama
phantosmax

CloudStack MCP Server

by phantosmax

stop_virtual_machine

Stop a virtual machine on the CloudStack MCP Server by providing its ID, with an optional parameter to force the shutdown.

Instructions

Stop a virtual machine

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
forcedNoForce stop the VM
idYesVM ID to stop

Implementation Reference

  • The main handler function that executes the stop_virtual_machine tool logic. It calls the CloudStack client to stop the VM and formats a response message with the job ID.
    async handleStopVirtualMachine(args: any) {
      const result = await this.cloudStackClient.stopVirtualMachine({
        id: args.id,
        forced: args.forced || false
      });
      
      return {
        content: [
          {
            type: 'text',
            text: `Stopped virtual machine ${args.id}. Job ID: ${result.stopvirtualmachineresponse?.jobid}`
          }
        ]
      };
    }
  • The tool schema definition including name, description, and input validation schema for the stop_virtual_machine tool.
    {
      name: 'stop_virtual_machine',
      description: 'Stop a virtual machine',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'string',
            description: 'VM ID to stop',
          },
          forced: {
            type: 'boolean',
            description: 'Force stop the VM',
            default: false,
          },
        },
        required: ['id'],
        additionalProperties: false,
      },
  • src/server.ts:114-115 (registration)
    Registration/dispatch of the stop_virtual_machine tool in the MCP server request handler switch statement.
    case 'stop_virtual_machine':
      return await this.vmHandlers.handleStopVirtualMachine(args);
  • Helper method in CloudStackClient that makes the actual API request to stopVirtualMachine in CloudStack.
    async stopVirtualMachine(params: CloudStackParams): Promise<CloudStackResponse> {
      return this.request('stopVirtualMachine', 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 for behavioral disclosure. It states the action ('Stop') but doesn't explain what 'stop' entails (e.g., graceful shutdown vs. power-off, effect on billing or resources, whether it's reversible via 'start_virtual_machine', or any side effects). 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 no wasted words. It's front-loaded with the core action and resource, making it efficient and easy to parse, though this brevity contributes to gaps in other dimensions.

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 doesn't cover behavioral aspects (e.g., safety, reversibility), usage context, or output expectations, leaving the agent with insufficient information to use the tool effectively beyond basic syntax.

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 schema fully documents both parameters ('id' and 'forced'). The description adds no additional parameter semantics beyond what's in the schema, such as explaining when to use 'forced' or format examples for 'id'. This meets 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 ('Stop') and resource ('a virtual machine'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'reboot_virtual_machine' or 'start_virtual_machine' beyond the obvious verb difference, missing an opportunity to clarify scope or behavior distinctions.

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 'reboot_virtual_machine' or 'start_virtual_machine'. It lacks context about prerequisites (e.g., VM must be running), consequences (e.g., stops all processes), or typical use cases (e.g., maintenance vs. emergency stop).

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