Skip to main content
Glama
ahmedselimmansor-ctrl

IBM Cloud MCP Server

vpc_list_volumes

List block storage volumes in IBM Cloud VPC, with optional filters by region, zone, or limit.

Instructions

List block storage volumes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
zone_nameNo
regionNo

Implementation Reference

  • Registration of the vpc_list_volumes tool via server.tool() with schema and handler.
    server.tool("vpc_list_volumes", "List block storage volumes", {
      limit: z.number().optional(), zone_name: z.string().optional(), region: z.string().optional(),
    }, async (p) => safeTool(() => client.get(vpcUrl(p.region||r, "/volumes"), {limit:p.limit,"zone.name":p.zone_name})));
  • Input schema: optional 'limit' (number), 'zone_name' (string), and 'region' (string).
    limit: z.number().optional(), zone_name: z.string().optional(), region: z.string().optional(),
  • Handler: async lambda that calls client.get() on the VPC volumes API endpoint, passing limit and zone.name query params. Wrapped in safeTool for error handling.
    }, async (p) => safeTool(() => client.get(vpcUrl(p.region||r, "/volumes"), {limit:p.limit,"zone.name":p.zone_name})));
  • The vpcUrl helper builds the full VPC API URL with region, path, 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`;
    }
  • The safeTool helper wraps the handler to catch errors and return structured MCP success/error responses.
    export async function safeTool<T>(fn: () => Promise<T>): Promise<ReturnType<typeof successContent> | ReturnType<typeof errorContent>> {
      try {
        const result = await fn();
        return successContent(result);
      } catch (error) {
        return errorContent(error);
      }
    }
Behavior2/5

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

With no annotations, the description carries the full burden. It fails to disclose any behavioral traits such as pagination, ordering, region/zone scoping, or authentication needs. The minimal description does not go beyond the name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (a single phrase), which aids quick reading. However, it lacks any structural organization or additional sentences to provide context. It is under-specified rather than efficiently concise.

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?

Given the tool has 3 optional parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain output format, filtering capabilities, or usage constraints, leaving the agent without sufficient information.

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?

Schema description coverage is 0%, and the description does not explain the purpose or format of any of the three parameters (limit, zone_name, region). It adds no meaning beyond the input schema.

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 'List block storage volumes' uses a specific verb and resource, making the tool's primary function clear. It distinguishes from siblings like vpc_list_instances by mentioning 'block storage volumes', but does not explicitly differentiate from other volume-related tools.

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 like vpc_create_volume or vpc_list_subnets. There is no mention of prerequisites, filtering, or context.

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