Skip to main content
Glama
ahmedselimmansor-ctrl

IBM Cloud MCP Server

db_delete_deployment

Remove a database deployment by providing its resource instance ID.

Instructions

Delete a database deployment

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instance_idYesResource instance ID

Implementation Reference

  • Handler function that executes the db_delete_deployment tool logic: checks write permission, sends a DELETE request to the IBM Cloud Resource Controller API for the given instance_id, and returns a success message.
    server.tool("db_delete_deployment", "Delete a database deployment", {
      instance_id: z.string().describe("Resource instance ID"),
    }, async (p) => safeTool(async () => { w();
      await client.delete(`${IBM_ENDPOINTS.RESOURCE_CONTROLLER}/resource_instances/${p.instance_id}`);
      return {message:"Database deployment deleted"};
    }));
  • Input schema for db_delete_deployment: requires a single 'instance_id' string parameter describing the resource instance ID.
      instance_id: z.string().describe("Resource instance ID"),
    }, async (p) => safeTool(async () => { w();
  • Registration of the db_delete_deployment tool on the MCP server via server.tool(), within the registerDatabaseTools function.
    server.tool("db_delete_deployment", "Delete a database deployment", {
      instance_id: z.string().describe("Resource instance ID"),
    }, async (p) => safeTool(async () => { w();
      await client.delete(`${IBM_ENDPOINTS.RESOURCE_CONTROLLER}/resource_instances/${p.instance_id}`);
      return {message:"Database deployment deleted"};
    }));
  • src/server.ts:65-66 (registration)
    The registerDatabaseTools function is called from createServer() in server.ts, which registers all database tools including db_delete_deployment.
    registerDatabaseTools(server, client, config);
    console.error(`  ✓ Databases (10 tools)`);
  • Helper function assertWriteAllowed used by the handler to enforce read-only mode; throws WriteNotAllowedError if writes are disabled.
    export function assertWriteAllowed(allowWrite: boolean): void {
      if (!allowWrite) {
        throw new WriteNotAllowedError();
      }
    }
Behavior2/5

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

No annotations provided, so description must disclose behavior. It fails to indicate that deletion is destructive, irreversible, or any side effects like cascade deletions. Simply stating 'Delete' is insufficient.

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

Conciseness4/5

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

Single sentence with no wasted words. However, extreme brevity sacrifices important behavioral context, though it is structurally concise.

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?

Simple tool with one parameter and no output schema. Still, description should convey that deletion is irreversible or requires confirmation. Current description feels incomplete for a destructive operation.

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 coverage is 100% with description for instance_id. The description adds no additional meaning beyond the schema's 'Resource instance ID', meeting the baseline for high coverage.

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 verb 'Delete' and the resource 'database deployment', distinguishing it from sibling operations like create, get, list. No ambiguity.

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 vs alternatives, no mention of prerequisites, irreversible nature, or when not to use. The description is purely definitional.

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