Skip to main content
Glama
ahmedselimmansor-ctrl

IBM Cloud MCP Server

db_list_connections

Retrieve database connection strings for a deployment by specifying the deployment ID, with optional user type, user ID, and region.

Instructions

Get connection strings for a database

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deployment_idYes
user_typeNoUser type (default: database)
user_idNo
regionNo

Implementation Reference

  • Registration of the 'db_list_connections' tool on the MCP server with its schema (deployment_id, user_type, user_id, region).
    server.tool("db_list_connections", "Get connection strings for a database", {
      deployment_id: z.string(), user_type: z.string().optional().describe("User type (default: database)"),
      user_id: z.string().optional(), region: z.string().optional(),
    }, async (p) => safeTool(() =>
      client.get(`${base(p.region||r)}/deployments/${encodeURIComponent(p.deployment_id)}/users/${p.user_type||"database"}/${p.user_id||"admin"}/connections`)
    ));
  • Input schema definition for the tool: deployment_id (required string), user_type (optional string, default 'database'), user_id (optional string), region (optional string).
    server.tool("db_list_connections", "Get connection strings for a database", {
      deployment_id: z.string(), user_type: z.string().optional().describe("User type (default: database)"),
      user_id: z.string().optional(), region: z.string().optional(),
  • Handler function that makes a GET request to the IBM Cloud Databases API to retrieve connection strings for a given deployment and user.
    }, async (p) => safeTool(() =>
      client.get(`${base(p.region||r)}/deployments/${encodeURIComponent(p.deployment_id)}/users/${p.user_type||"database"}/${p.user_id||"admin"}/connections`)
    ));
Behavior2/5

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

With no annotations, the description must convey behavioral traits. It only implies a read operation ('Get'), but does not disclose potential errors, authentication requirements, or response structure.

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?

The description is a single concise sentence with no wasted words. However, it is arguably too terse for a tool with 4 parameters.

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?

Given the 4 parameters and no output schema, the description is insufficient. It lacks information on prerequisites, ordering, or what the returned connection strings contain.

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 description coverage is low (25%), and the description does not add meaning. Only 'user_type' has a description; others like 'deployment_id' and 'region' are left unexplained, and the description does not compensate.

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 action 'Get' and the resource 'connection strings for a database', which is specific and distinguishes it from sibling database tools like db_get_deployment or db_list_backups.

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 vs. alternatives such as db_get_deployment or db_list_deployments. There is no mention of prerequisites or context.

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