Skip to main content
Glama
phantosmax

CloudStack MCP Server

by phantosmax

create_snapshot

Generate a snapshot of a specified volume in Apache CloudStack using the CloudStack MCP Server, ensuring data preservation and recovery readiness by providing the volume ID and optional snapshot name.

Instructions

Create a snapshot of a volume

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoSnapshot name
volumeidYesVolume ID to snapshot

Implementation Reference

  • The handler function that executes the create_snapshot tool logic. It calls the CloudStack client to create the snapshot and returns a formatted text response with job ID and snapshot ID.
    async handleCreateSnapshot(args: any) {
      const result = await this.cloudStackClient.createSnapshot(args);
      
      return {
        content: [
          {
            type: 'text',
            text: `Created snapshot of volume ${args.volumeid}. Job ID: ${result.createsnapshotresponse?.jobid}\nSnapshot ID: ${result.createsnapshotresponse?.id}`
          }
        ]
      };
    }
  • Input schema definition for the create_snapshot tool, specifying required volumeid and optional name.
    {
      name: 'create_snapshot',
      description: 'Create a snapshot of a volume',
      inputSchema: {
        type: 'object',
        properties: {
          volumeid: {
            type: 'string',
            description: 'Volume ID to snapshot',
          },
          name: {
            type: 'string',
            description: 'Snapshot name',
          },
        },
        required: ['volumeid'],
        additionalProperties: false,
      },
    },
  • src/server.ts:144-145 (registration)
    Tool registration/dispatch in the MCP server: maps 'create_snapshot' calls to the storage handler.
    case 'create_snapshot':
      return await this.storageHandlers.handleCreateSnapshot(args);
  • Helper method in CloudStack client that makes the underlying API request for createSnapshot.
    async createSnapshot(params: CloudStackParams): Promise<CloudStackResponse> {
      return this.request('createSnapshot', params);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Create a snapshot' which implies a write/mutation operation, but doesn't mention any behavioral traits such as whether this is an asynchronous operation, if it requires specific permissions, potential impacts on the volume (e.g., brief performance degradation), or what the expected output might be. For a mutation tool with zero annotation coverage, this is inadequate.

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 5 words, front-loading the essential information ('Create a snapshot of a volume') with zero wasted words. Every element earns its place, making it efficient for quick understanding.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after creation (e.g., snapshot state, return values), potential side effects, or usage constraints. For a tool that creates resources in a system, more context about behavior and outcomes is needed.

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 both parameters ('name' and 'volumeid') with their descriptions. The tool description adds no additional parameter semantics beyond what's in the schema, but since the schema coverage is complete, the baseline score of 3 is appropriate.

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 ('Create a snapshot') and the target resource ('of a volume'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'list_snapshots' or 'create_volume', which would require mentioning this is a write operation that creates a new snapshot rather than listing existing ones.

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. It doesn't mention prerequisites (e.g., the volume must exist and be in a suitable state), when not to use it (e.g., during certain operations), or how it differs from related tools like 'list_snapshots' or 'create_volume'.

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