Skip to main content
Glama
ahmedselimmansor-ctrl

IBM Cloud MCP Server

db_get_scaling

Retrieve the current scaling configuration of a deployment, including group ID and region details.

Instructions

Get current scaling configuration for a deployment

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deployment_idYes
group_idNoGroup ID (default: member)
regionNo

Implementation Reference

  • The handler function for 'db_get_scaling' tool that performs a GET request to the IBM Cloud Databases API endpoint to retrieve scaling configuration for a deployment group. It calls client.get() with the URL formed from the database base endpoint, deployment_id, and group_id (defaulting to 'member').
    server.tool("db_get_scaling", "Get current scaling configuration for a deployment", {
      deployment_id: z.string(), group_id: z.string().optional().describe("Group ID (default: member)"),
      region: z.string().optional(),
    }, async (p) => safeTool(() =>
      client.get(`${base(p.region||r)}/deployments/${encodeURIComponent(p.deployment_id)}/groups/${p.group_id||"member"}`)
    ));
  • Zod schema defining the input parameters for 'db_get_scaling': deployment_id (required string), group_id (optional string, defaults to 'member'), and region (optional string).
    deployment_id: z.string(), group_id: z.string().optional().describe("Group ID (default: member)"),
    region: z.string().optional(),
  • Registration of 'db_get_scaling' tool via server.tool() in the registerDatabaseTools function, which is called from src/server.ts line 65.
    server.tool("db_get_scaling", "Get current scaling configuration for a deployment", {
      deployment_id: z.string(), group_id: z.string().optional().describe("Group ID (default: member)"),
      region: z.string().optional(),
    }, async (p) => safeTool(() =>
      client.get(`${base(p.region||r)}/deployments/${encodeURIComponent(p.deployment_id)}/groups/${p.group_id||"member"}`)
    ));
  • The DATABASES endpoint helper in IBM_ENDPOINTS that constructs the base URL for the IBM Cloud Databases API (v5). Used by the tool to form the API request URL.
    DATABASES: (region: string) =>
      `https://api.${region}.databases.cloud.ibm.com/v5/ibm`,
  • The safeTool helper that wraps the handler logic, catching errors and returning proper MCP success/error content blocks.
    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 only states it's a 'get' operation, implying read-only. It does not disclose idempotency, side effects, required permissions, rate limits, or return format, which are critical for a tool with no annotation support.

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

Conciseness5/5

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

The description is a single, clear sentence with no extraneous information. It is appropriately concise for a simple get operation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is adequate for a straightforward get tool, but it lacks details about what the scaling configuration includes (e.g., CPU, memory, replicas). Given no output schema, more context would help.

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 33% (only 'group_id' has a description). The tool description does not elaborate on parameter semantics beyond what the schema provides, failing to compensate for the low 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 clearly states the verb 'get', the resource 'scaling configuration', and the context 'for a deployment'. It distinguishes itself from the sibling tool 'db_set_scaling' as the read counterpart.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context (when you need scaling config) but does not provide explicit guidance on when to use vs. alternatives like 'db_get_deployment' or 'db_list_deployments'. No when-not or alternative tool mentions.

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