Skip to main content
Glama
phantosmax

CloudStack MCP Server

by phantosmax

list_service_offerings

Retrieve and filter compute plans (service offerings) on the CloudStack MCP Server, enabling efficient resource management by listing available configurations based on domain or system criteria.

Instructions

List service offerings (compute plans)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainidNoDomain ID to filter offerings
issystemNoShow system offerings

Implementation Reference

  • The main handler function that executes the tool logic: fetches service offerings from CloudStack client and formats them into a structured text response.
    async handleListServiceOfferings(args: any) {
      const result = await this.cloudStackClient.listServiceOfferings(args);
      const offerings = result.listserviceofferingsresponse?.serviceoffering || [];
      
      const offeringList = offerings.map((offering: any) => ({
        id: offering.id,
        name: offering.name,
        displaytext: offering.displaytext,
        cpunumber: offering.cpunumber,
        cpuspeed: offering.cpuspeed,
        memory: offering.memory,
        storagetype: offering.storagetype,
        iscustomized: offering.iscustomized,
        issystem: offering.issystem,
        created: offering.created
      }));
    
      return {
        content: [
          {
            type: 'text',
            text: `Found ${offeringList.length} service offerings:\n\n${offeringList
              .map((offering: any) => 
                `• ${offering.name} (${offering.id})\n  Display Text: ${offering.displaytext}\n  CPUs: ${offering.cpunumber} @ ${offering.cpuspeed}MHz\n  Memory: ${offering.memory}MB\n  Storage Type: ${offering.storagetype}\n  Customized: ${offering.iscustomized}\n  System: ${offering.issystem}\n  Created: ${offering.created}\n`
              )
              .join('\n')}`
          }
        ]
      };
    }
  • Tool definition with name, description, and input schema specifying optional parameters issystem and domainid.
      name: 'list_service_offerings',
      description: 'List service offerings (compute plans)',
      inputSchema: {
        type: 'object',
        properties: {
          issystem: {
            type: 'boolean',
            description: 'Show system offerings',
            default: false,
          },
          domainid: {
            type: 'string',
            description: 'Domain ID to filter offerings',
          },
        },
        additionalProperties: false,
      },
    },
  • src/server.ts:196-197 (registration)
    MCP server switch case that registers and dispatches the tool call to the corresponding admin handler method.
    case 'list_service_offerings':
      return await this.adminHandlers.handleListServiceOfferings(args);
  • CloudStack client helper method that sends the 'listServiceOfferings' API request to the CloudStack server.
    async listServiceOfferings(params: CloudStackParams = {}): Promise<CloudStackResponse> {
      return this.request('listServiceOfferings', params);
    }
Behavior2/5

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

With no annotations, the description carries full burden but only states the action without behavioral details. It doesn't disclose if this is a read-only operation, pagination behavior, rate limits, authentication needs, or what 'compute plans' entail, which is insufficient for a tool with potential complexity.

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 no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly, which is ideal for conciseness.

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 and no output schema, the description is incomplete. It lacks details on return values, error handling, or operational context (e.g., how offerings relate to other resources), making it inadequate for a tool that might be part of a larger provisioning workflow.

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 description adds no parameter information beyond the input schema, which has 100% coverage with clear descriptions for both parameters. This meets the baseline of 3, as the schema adequately documents the parameters without needing extra detail from the 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 ('service offerings'), with additional context in parentheses ('compute plans') that clarifies the domain. It distinguishes from siblings like 'list_virtual_machines' or 'list_templates' by specifying the resource type, though it doesn't explicitly contrast with them.

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. It doesn't mention prerequisites, context (e.g., for provisioning resources), or exclusions, leaving the agent to infer usage from the tool name alone among many list-related siblings.

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