Skip to main content
Glama
phantosmax

CloudStack MCP Server

by phantosmax

reset_password_virtual_machine

Reset the password for a virtual machine by specifying its VM ID using this tool within the CloudStack MCP Server for streamlined cloud resource management.

Instructions

Reset password for virtual machine

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesVM ID

Implementation Reference

  • The core handler function that implements the tool logic by calling the CloudStack client to reset the VM password and returning a success message with job ID.
    async handleResetPasswordVirtualMachine(args: any) {
      const result = await this.cloudStackClient.resetPasswordForVirtualMachine({ id: args.id });
      
      return {
        content: [
          {
            type: 'text',
            text: `Reset password for virtual machine ${args.id}. Job ID: ${result.resetpasswordforvirtualmachineresponse?.jobid}`
          }
        ]
      };
    }
  • The tool definition including name, description, and input schema that validates the 'id' parameter.
      name: 'reset_password_virtual_machine',
      description: 'Reset password for virtual machine',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'string',
            description: 'VM ID',
          },
        },
        required: ['id'],
        additionalProperties: false,
      },
    },
  • src/server.ts:126-127 (registration)
    Tool registration in the server dispatch logic, routing calls to the virtual machine handler.
    case 'reset_password_virtual_machine':
      return await this.vmHandlers.handleResetPasswordVirtualMachine(args);
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 offers minimal behavioral insight. It implies a mutation (password reset) but doesn't disclose critical details like whether this requires admin permissions, if it triggers a reboot, what happens to existing sessions, or error conditions. This is inadequate for a mutation tool with zero annotation coverage.

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

For a mutation tool with no annotations and no output schema, the description is insufficient. It lacks details on behavioral traits (e.g., side effects, permissions), expected outcomes, or error handling, leaving significant gaps for the agent to operate 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?

The schema description coverage is 100%, with the single parameter 'id' documented as 'VM ID' in the schema. The description adds no additional parameter context beyond what's already in the schema, so it meets the baseline score of 3 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 verb ('Reset password') and resource ('for virtual machine'), making the purpose immediately understandable. It doesn't specifically differentiate from siblings like 'reboot_virtual_machine' or 'stop_virtual_machine', but the action is distinct enough that confusion is unlikely.

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. The description doesn't mention prerequisites (e.g., VM state), exclusions, or related tools like 'deploy_virtual_machine' for initial setup, leaving the agent to infer usage context.

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