Skip to main content
Glama
ahmedselimmansor-ctrl

IBM Cloud MCP Server

cos_get_bucket_config

Retrieve bucket configuration and metadata from IBM Cloud Object Storage using bucket name and instance CRN.

Instructions

Get bucket configuration and metadata

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bucket_nameYes
instance_crnYes

Implementation Reference

  • Handler function for cos_get_bucket_config tool - makes a GET request to the COS configuration API endpoint with the bucket name and instance CRN.
    }, async (p) => safeTool(() =>
      client.request(`${cfgBase}/b/${p.bucket_name}`, {headers:{"ibm-service-instance-id":p.instance_crn}})
    ));
  • Input schema for cos_get_bucket_config - requires bucket_name and instance_crn parameters.
    bucket_name: z.string(), instance_crn: z.string(),
  • Registration of cos_get_bucket_config tool using the MCP server.tool() method, with description, input schema, and handler.
    server.tool("cos_get_bucket_config", "Get bucket configuration and metadata", {
      bucket_name: z.string(), instance_crn: z.string(),
    }, async (p) => safeTool(() =>
      client.request(`${cfgBase}/b/${p.bucket_name}`, {headers:{"ibm-service-instance-id":p.instance_crn}})
    ));
  • src/server.ts:59-60 (registration)
    Registration of all COS tools (including cos_get_bucket_config) from server.ts.
    registerCOSTools(server, client, config);
    console.error(`  ✓ Cloud Object Storage (12 tools)`);
  • cfgBase is set to IBM_ENDPOINTS.COS_CONFIG which resolves to 'https://config.cloud-object-storage.cloud.ibm.com/v1', the base URL used in the cos_get_bucket_config handler.
    const cfgBase = IBM_ENDPOINTS.COS_CONFIG;
Behavior2/5

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

No annotations provided; description only states the operation without disclosing behavioral traits like idempotency, auth requirements, or side effects.

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

Conciseness2/5

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

Extremely short (4 words) but at the cost of informativeness. It is under-specified and leaves out important context.

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?

No output schema, no annotations, and minimal description. For a simple tool with only 2 parameters, the description does not provide enough context for an agent to understand what configuration or metadata is returned.

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?

Schema has 2 parameters with 0% description coverage. Description adds no meaning beyond the parameter names, failing to compensate for the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it gets bucket configuration and metadata. Among siblings like cos_list_buckets and cos_get_object_metadata, it is distinct, though it could be more specific.

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 like cos_list_buckets or cos_get_object_metadata. No context for appropriate usage.

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