Skip to main content
Glama
ahmedselimmansor-ctrl

IBM Cloud MCP Server

vpc_create_volume

Create a block storage volume in IBM Cloud VPC by specifying name, zone, capacity in GB, and optionally profile and region.

Instructions

Create a block storage volume

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
zoneYes
capacityYesGB
profileNoe.g. general-purpose
regionNo

Implementation Reference

  • Registration of the 'vpc_create_volume' tool on the MCP server using server.tool(). Defines the tool name, description, input schema (name, zone, capacity, profile, region), and the handler callback.
    server.tool("vpc_create_volume", "Create a block storage volume", {
      name: z.string(), zone: z.string(), capacity: z.number().describe("GB"),
      profile: z.string().optional().describe("e.g. general-purpose"), region: z.string().optional(),
    }, async (p) => safeTool(async () => { w();
      return client.post(vpcUrl(p.region||r, "/volumes"), {name:p.name,zone:{name:p.zone},capacity:p.capacity,profile:{name:p.profile||"general-purpose"}});
    }));
  • The handler function for vpc_create_volume. It calls assertWriteAllowed (via w()), then posts to the IBM Cloud VPC API /volumes endpoint with the provided name, zone, capacity, and profile parameters.
    }, async (p) => safeTool(async () => { w();
      return client.post(vpcUrl(p.region||r, "/volumes"), {name:p.name,zone:{name:p.zone},capacity:p.capacity,profile:{name:p.profile||"general-purpose"}});
    }));
  • Input schema definition using Zod for vpc_create_volume. Defines required fields: name (string), zone (string), capacity (number, GB); and optional fields: profile (string, e.g. general-purpose), region (string).
    name: z.string(), zone: z.string(), capacity: z.number().describe("GB"),
    profile: z.string().optional().describe("e.g. general-purpose"), region: z.string().optional(),
  • assertWriteAllowed helper - called by the handler to verify write operations are allowed before making the API call.
    export function assertWriteAllowed(allowWrite: boolean): void {
      if (!allowWrite) {
        throw new WriteNotAllowedError();
      }
    }
  • vpcUrl helper - constructs the full VPC API URL for the given region and path (e.g., /volumes) with version and generation query parameters.
    export function vpcUrl(region: string, path: string, version: string = "2024-11-19"): string {
      const base = `https://${region}.iaas.cloud.ibm.com/v1${path}`;
      const sep = base.includes("?") ? "&" : "?";
      return `${base}${sep}version=${version}&generation=2`;
    }
Behavior2/5

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

With no annotations, the description carries full burden but fails to disclose behavioral traits such as whether the volume is created synchronously, any size limits, or data durability guarantees. The statement is too brief to inform safe usage.

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, short sentence with no extraneous words. It is maximally concise, though at the cost of completeness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 5 parameters (3 required), no output schema, and no annotations, the description is severely incomplete. It omits return values, side effects, and dependencies, making it insufficient for an AI agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds no information about parameters beyond the input schema. Schema coverage is only 40%, yet the description does not elaborate on the meaning of 'name', 'zone', or 'region', leaving the agent with minimal guidance.

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

Purpose3/5

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

The description 'Create a block storage volume' is a verb+noun but lacks specificity to distinguish it from sibling tools like vpc_create_instance or vpc_create_subnet. It does not mention unique aspects such as volume type, size, or zone.

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. There is no mention of prerequisites (e.g., existing VPC or subnet) or conditions that would make a different tool more 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

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/ahmedselimmansor-ctrl/IBM_cloud_MCP_SERVER'

If you have feedback or need assistance with the MCP directory API, please join our Discord server