Skip to main content
Glama
ahmedselimmansor-ctrl

IBM Cloud MCP Server

vpc_delete_volume

Delete an IBM Cloud VPC volume by specifying its volume ID. Optionally include the region to target a specific location.

Instructions

Delete a volume

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
volume_idYes
regionNo

Implementation Reference

  • Registration of the vpc_delete_volume tool on the MCP server with schema and handler
    server.tool("vpc_delete_volume", "Delete a volume", {
      volume_id: z.string(), region: z.string().optional(),
    }, async (p) => safeTool(async () => { w(); await client.delete(vpcUrl(p.region||r, `/volumes/${p.volume_id}`)); return {message:"Volume deleted"}; }));
  • Input schema: volume_id (string, required) and region (string, optional)
    volume_id: z.string(), region: z.string().optional(),
  • Handler function: performs write-allowed check, then issues delete request to /volumes/{volume_id} and returns success message
    }, async (p) => safeTool(async () => { w(); await client.delete(vpcUrl(p.region||r, `/volumes/${p.volume_id}`)); return {message:"Volume deleted"}; }));
  • safeTool helper wraps handler to catch errors and return proper MCP 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);
      }
    }
  • src/server.ts:7-8 (registration)
    Import of registerVPCTools in the main server entry point
    import { registerIAMTools } from "./tools/iam/index.js";
    import { registerVPCTools } from "./tools/vpc/index.js";
Behavior2/5

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

The description only states 'Delete', offering no behavioral details like irreversibility, permission requirements, or failure conditions (e.g., volume attached). With no annotations, the description fails to disclose key traits.

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

Conciseness2/5

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

The description is a minimal phrase, but conciseness should not sacrifice essential information. It is under-specified and lacks structure, failing to earn its place by providing value.

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 lack of annotations and output schema, the description is severely incomplete. It omits critical context like required state of the volume, error scenarios, and result expectations.

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

Parameters2/5

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

The input schema has 0% description coverage, and the description adds no meaning to the parameters volume_id and region beyond their names. The agent cannot infer expected formats or constraints.

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

Purpose5/5

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

The description 'Delete a volume' uses a specific verb and resource, clearly indicating the action and object. Among sibling tools like vpc_create_volume and vpc_list_volumes, it effectively distinguishes itself.

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, such as when a volume must be detached or if there are prerequisites. The description lacks any usage 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