Skip to main content
Glama
phantosmax

CloudStack MCP Server

by phantosmax

list_storage_pools

Retrieve and filter storage pools in CloudStack MCP Server by specifying Zone ID or Cluster ID for efficient cloud resource management.

Instructions

List storage pools

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clusteridNoCluster ID to filter storage pools
zoneidNoZone ID to filter storage pools

Implementation Reference

  • The main handler function that executes the list_storage_pools tool logic. It fetches storage pools via CloudStack client, maps relevant fields, and returns a formatted text response listing pools with details like name, ID, type, state, zone, cluster, IP, path, and disk usage.
    async handleListStoragePools(args: any) {
      const result = await this.cloudStackClient.listStoragePools(args);
      const pools = result.liststoragepoolsresponse?.storagepool || [];
      
      const poolList = pools.map((pool: any) => ({
        id: pool.id,
        name: pool.name,
        type: pool.type,
        state: pool.state,
        zonename: pool.zonename,
        clustername: pool.clustername,
        ipaddress: pool.ipaddress,
        path: pool.path,
        disksizeused: pool.disksizeused,
        disksizetotal: pool.disksizetotal
      }));
    
      return {
        content: [
          {
            type: 'text',
            text: `Found ${poolList.length} storage pools:\n\n${poolList
              .map((pool: any) => 
                `• ${pool.name} (${pool.id})\n  Type: ${pool.type}\n  State: ${pool.state}\n  Zone: ${pool.zonename}\n  Cluster: ${pool.clustername}\n  IP: ${pool.ipaddress}\n  Path: ${pool.path}\n  Usage: ${pool.disksizeused}/${pool.disksizetotal} GB\n`
              )
              .join('\n')}`
          }
        ]
      };
    }
  • Tool schema definition specifying the name, description, and input schema allowing optional zoneid and clusterid filters.
    {
      name: 'list_storage_pools',
      description: 'List storage pools',
      inputSchema: {
        type: 'object',
        properties: {
          zoneid: {
            type: 'string',
            description: 'Zone ID to filter storage pools',
          },
          clusterid: {
            type: 'string',
            description: 'Cluster ID to filter storage pools',
          },
        },
        additionalProperties: false,
      },
    },
  • src/server.ts:192-193 (registration)
    Registration and dispatch logic in the MCP server that maps the tool name to the corresponding admin handler method.
    case 'list_storage_pools':
      return await this.adminHandlers.handleListStoragePools(args);
  • Supporting utility method in CloudStackClient that performs the actual API request to the 'listStoragePools' CloudStack endpoint.
    async listStoragePools(params: CloudStackParams = {}): Promise<CloudStackResponse> {
      return this.request('listStoragePools', 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 for behavioral disclosure. 'List storage pools' implies a read-only operation but doesn't specify whether it returns all pools or requires filtering, pagination behavior, authentication needs, rate limits, or error conditions. For a tool with no annotation coverage, this minimal description fails to provide necessary operational context.

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 two words, with zero wasted language. It's front-loaded with the core action ('List') and resource ('storage pools'), making it easy to parse. While under-specified, every word earns its place by stating the basic function without redundancy.

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 the tool's complexity (a list operation with filtering parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what a storage pool is, how results are returned, whether filtering is required, or any behavioral aspects. For a tool in a crowded namespace of list_* siblings, this minimal description leaves significant gaps for agent understanding.

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%, with both parameters (clusterid, zoneid) clearly documented in the schema. The description adds no parameter information beyond what's in the schema, so it doesn't compensate but also doesn't detract. According to scoring rules, when schema coverage is high (>80%), the baseline score is 3 even with no param info in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List storage pools' is a tautology that merely restates the tool name without adding specificity. It doesn't distinguish this tool from its many sibling list_* tools (like list_volumes, list_networks, etc.), nor does it clarify what a 'storage pool' is in this context. While the verb 'List' is clear, the resource 'storage pools' lacks differentiation from similar resources in the sibling set.

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 any prerequisites, context for filtering (e.g., when to use clusterid vs zoneid), or relationships to other tools (like list_volumes or list_capacity). With many list_* siblings, this omission leaves the agent without direction on tool selection.

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