Skip to main content
Glama
ahmedselimmansor-ctrl

IBM Cloud MCP Server

vpc_release_floating_ip

Release a floating IP to disassociate it from a resource and make it available for reuse.

Instructions

Release a floating IP

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fip_idYes
regionNo

Implementation Reference

  • The tool handler for vpc_release_floating_ip. Calls client.delete on the floating_ips endpoint with the provided fip_id, after asserting write permissions.
    server.tool("vpc_release_floating_ip", "Release a floating IP", {
      fip_id: z.string(), region: z.string().optional(),
    }, async (p) => safeTool(async () => { w(); await client.delete(vpcUrl(p.region||r, `/floating_ips/${p.fip_id}`)); return {message:"Floating IP released"}; }));
  • Input schema for vpc_release_floating_ip: requires fip_id (string) and optional region (string).
    fip_id: z.string(), region: z.string().optional(),
  • Registration of the tool via server.tool() call inside registerVPCTools().
    server.tool("vpc_release_floating_ip", "Release a floating IP", {
  • src/server.ts:53-53 (registration)
    registerVPCTools is called from the main server.ts to register all VPC tools including vpc_release_floating_ip.
    registerVPCTools(server, client, config);
  • The vpcUrl helper function constructs the VPC API URL with version parameter, used by the handler.
    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`;
    }
Behavior1/5

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

No annotations present, so description must disclose behavioral traits. It merely says 'release' without explaining consequences: whether it disassociates, deletes, or requires IP to be unattached. This is a significant gap for a potentially destructive operation.

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?

Extremely concise at one sentence, but not structured. No wasted words, but lacks critical details that could be added without sacrificing brevity.

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?

For a simple 2-parameter tool with no output schema, the description is underspecified. Missing behavioral and parameter context makes it insufficient for an agent to invoke reliably without prior domain knowledge.

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 coverage is 0% and description adds no meaning to parameters. While 'fip_id' is somewhat self-explanatory, 'region' lacks context. Agent receives no help understanding required vs optional or valid values.

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?

Description clearly states the tool releases a floating IP, distinguishing it from sibling tools like vpc_reserve_floating_ip (allocates) and vpc_list_floating_ips (lists). The verb 'release' and resource 'floating IP' are specific and unambiguous.

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 on when to use this tool versus alternatives. No prerequisites mentioned (e.g., IP must be allocated, not attached). Sibling tools are listed but not referenced in the description.

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