Skip to main content
Glama
ahmedselimmansor-ctrl

IBM Cloud MCP Server

db_list_backups

Lists all available backups for a specified IBM Cloud database deployment using its deployment ID and optional region.

Instructions

List backups for a database deployment

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deployment_idYes
regionNo

Implementation Reference

  • The tool 'db_list_backups' is registered on the MCP server using server.tool() with the name 'db_list_backups' and description 'List backups for a database deployment'.
    server.tool("db_list_backups", "List backups for a database deployment", {
      deployment_id: z.string(), region: z.string().optional(),
    }, async (p) => safeTool(() => client.get(`${base(p.region||r)}/deployments/${encodeURIComponent(p.deployment_id)}/backups`)));
  • Input schema for 'db_list_backups': requires a 'deployment_id' (z.string()) and optional 'region' (z.string().optional()).
    deployment_id: z.string(), region: z.string().optional(),
  • The handler performs a GET request to the IBM Cloud Databases API endpoint: `${base(p.region||r)}/deployments/${encodeURIComponent(p.deployment_id)}/backups`, wrapped in safeTool() for error handling. The base URL is constructed using IBM_ENDPOINTS.DATABASES (https://api.{region}.databases.cloud.ibm.com/v5/ibm).
    }, async (p) => safeTool(() => client.get(`${base(p.region||r)}/deployments/${encodeURIComponent(p.deployment_id)}/backups`)));
  • The handler delegates to IBMCloudAPIClient.get() which makes an authenticated GET request to the provided URL with query parameters.
    async get<T = unknown>(url: string, queryParams?: Record<string, string | number | boolean | undefined>): Promise<T> {
      return this.request<T>(url, { method: "GET", queryParams });
    }
  • The safeTool() wrapper catches errors and formats successful/failed responses into MCP 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?

No annotations are present, so the description must carry the burden. It only states 'list', implying a read operation, but does not disclose any behavioral traits such as pagination, output format, or authentication requirements.

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 sentence of six words with no filler. It is maximally 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?

For a list tool with no output schema, the description should at least hint at the output (e.g., backup IDs, timestamps). It does not mention pagination, ordering, or any filtering capabilities beyond the two parameters.

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?

The input schema has 0% description coverage, and the tool description adds no information about the parameters (e.g., what 'region' does). The agent receives no semantic help beyond parameter names.

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 (list), resource (backups), and scope (for a database deployment). It distinguishes from sibling tools like db_list_deployments and db_create_backup.

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 like db_create_backup or db_restore_backup. There is no mention of prerequisites or exclusions.

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