Skip to main content
Glama
ahmedselimmansor-ctrl

IBM Cloud MCP Server

db_create_deployment

Creates a new database deployment on IBM Cloud. Supports services like PostgreSQL, Redis, MongoDB, MySQL, Elasticsearch, etcd, and RabbitMQ.

Instructions

Create a new database deployment

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
serviceYes
planNoPlan ID (default: standard)
resource_group_idNo
regionNo

Implementation Reference

  • src/server.ts:65-66 (registration)
    Registration of registerDatabaseTools which includes the db_create_deployment tool, called from the server setup.
    registerDatabaseTools(server, client, config);
    console.error(`  ✓ Databases (10 tools)`);
  • The tool handler for 'db_create_deployment' - validates schema inputs, checks write permissions, and POSTs to the IBM Cloud Resource Controller to create a database deployment.
    server.tool("db_create_deployment", "Create a new database deployment", {
      name: z.string(), service: z.enum(["databases-for-postgresql","databases-for-redis","databases-for-mongodb","databases-for-mysql","databases-for-elasticsearch","databases-for-etcd","messages-for-rabbitmq"]),
      plan: z.string().optional().describe("Plan ID (default: standard)"),
      resource_group_id: z.string().optional(), region: z.string().optional(),
    }, async (p) => safeTool(async () => { w();
      return client.post(`${IBM_ENDPOINTS.RESOURCE_CONTROLLER}/resource_instances`, {
        name:p.name, target:p.region||r, resource_plan_id:p.plan||"standard",
        resource_group:p.resource_group_id, service_name:p.service,
      });
    }));
  • Input schema for db_create_deployment: name (string), service (enum of database types), plan (optional string), resource_group_id (optional string), region (optional string).
    server.tool("db_create_deployment", "Create a new database deployment", {
      name: z.string(), service: z.enum(["databases-for-postgresql","databases-for-redis","databases-for-mongodb","databases-for-mysql","databases-for-elasticsearch","databases-for-etcd","messages-for-rabbitmq"]),
      plan: z.string().optional().describe("Plan ID (default: standard)"),
      resource_group_id: z.string().optional(), region: z.string().optional(),
  • The safeTool helper that wraps handler execution to catch errors and return proper 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);
      }
    }
  • The assertWriteAllowed helper that checks config.allowWrite before performing write operations like db_create_deployment.
    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?

The description does not disclose behavioral traits like idempotency, error handling, or required permissions. Without annotations, the agent has no insight into side effects or constraints.

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 a single sentence and is concise, but it lacks substance. It is front-loaded but provides minimal information.

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?

With no output schema, no annotations, and low schema coverage, the description fails to provide sufficient context for an agent to understand what the tool returns or how to use it effectively.

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?

Schema coverage is only 20%. The description adds no meaning to parameters (e.g., 'name', 'service', 'region'). It does not compensate for the low schema 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?

The description 'Create a new database deployment' clearly states the action (create) and the resource (database deployment), distinguishing it from sibling tools like db_create_backup or db_delete_deployment.

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 such as db_restore_backup or creating via resource_create_instance. No context on prerequisites or conditions.

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