Skip to main content
Glama
phantosmax

CloudStack MCP Server

by phantosmax

list_system_vms

Retrieve and filter system VMs (console proxy, secondary storage) by zone, type, and state in CloudStack infrastructure for streamlined management.

Instructions

List system VMs (console proxy, secondary storage)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateNoSystem VM state
systemvmtypeNoSystem VM type (consoleproxy, secondarystoragevm)
zoneidNoZone ID to filter system VMs

Implementation Reference

  • The handler function that executes the tool logic: calls CloudStack client to list system VMs, processes the response, and formats it as MCP content.
    async handleListSystemVms(args: any) {
      const result = await this.cloudStackClient.listSystemVms(args);
      const systemVms = result.listsystemvmsresponse?.systemvm || [];
      
      const systemVmList = systemVms.map((vm: any) => ({
        id: vm.id,
        name: vm.name,
        systemvmtype: vm.systemvmtype,
        state: vm.state,
        zonename: vm.zonename,
        hostid: vm.hostid,
        hostname: vm.hostname,
        publicip: vm.publicip,
        privateip: vm.privateip,
        linklocalip: vm.linklocalip
      }));
    
      return {
        content: [
          {
            type: 'text',
            text: `Found ${systemVmList.length} system VMs:\n\n${systemVmList
              .map((vm: any) => 
                `• ${vm.name} (${vm.id})\n  Type: ${vm.systemvmtype}\n  State: ${vm.state}\n  Zone: ${vm.zonename}\n  Host: ${vm.hostname}\n  Public IP: ${vm.publicip}\n  Private IP: ${vm.privateip}\n  Link Local IP: ${vm.linklocalip}\n`
              )
              .join('\n')}`
          }
        ]
      };
    }
  • Tool definition including name, description, and input schema for validation.
    {
      name: 'list_system_vms',
      description: 'List system VMs (console proxy, secondary storage)',
      inputSchema: {
        type: 'object',
        properties: {
          zoneid: {
            type: 'string',
            description: 'Zone ID to filter system VMs',
          },
          systemvmtype: {
            type: 'string',
            description: 'System VM type (consoleproxy, secondarystoragevm)',
          },
          state: {
            type: 'string',
            description: 'System VM state',
          },
        },
        additionalProperties: false,
      },
    },
  • src/server.ts:194-195 (registration)
    Dispatch/registration of the list_system_vms tool call to the admin handler in the MCP server switch statement.
    case 'list_system_vms':
      return await this.adminHandlers.handleListSystemVms(args);
  • CloudStack client wrapper method that performs the actual API request to listSystemVms.
    async listSystemVms(params: CloudStackParams = {}): Promise<CloudStackResponse> {
      return this.request('listSystemVms', params);
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states what the tool does (listing) without disclosing behavioral traits like pagination, rate limits, authentication requirements, or what happens if no VMs match filters. For a listing operation with zero annotation coverage, this is insufficient transparency.

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 - a single sentence that efficiently communicates the core purpose. Every word earns its place, with no redundant information. The structure is front-loaded with the main action and resource.

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 no annotations, no output schema, and multiple parameters, the description is incomplete. It doesn't explain what the tool returns, how results are formatted, or important behavioral aspects. For a listing tool in a complex infrastructure management context with many sibling tools, more context is needed for the agent to use it 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 schema already documents all three parameters. The description doesn't add any parameter-specific information beyond what's in the schema. According to guidelines, when schema coverage is high (>80%), the baseline score is 3 even with no param info in description.

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 ('List') and resource ('system VMs') with specific examples of what types are included ('console proxy, secondary storage'). It distinguishes from generic VM listing tools like 'list_virtual_machines' by focusing on system infrastructure VMs. However, it doesn't explicitly contrast with all sibling tools, keeping it at 4 instead of 5.

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, appropriate contexts, or exclusions. With many sibling tools for managing VMs and infrastructure, the lack of usage guidance leaves the agent uncertain about when this specific listing tool is appropriate.

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