Skip to main content
Glama
ahmedselimmansor-ctrl

IBM Cloud MCP Server

cos_delete_object

Delete an object from a Cloud Object Storage bucket by specifying the bucket name and object key.

Instructions

Delete an object from a bucket

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bucket_nameYes
object_keyYes
regionNo

Implementation Reference

  • The handler function for the 'cos_delete_object' tool. It sends an HTTP DELETE request to the S3 endpoint for the given bucket/object and returns a success message.
    server.tool("cos_delete_object", "Delete an object from a bucket", {
      bucket_name: z.string(), object_key: z.string(), region: z.string().optional(),
    }, async (p) => safeTool(async () => { w();
      await client.request(`${s3(p.region||r)}/${p.bucket_name}/${encodeURIComponent(p.object_key)}`, {method:"DELETE"});
      return {message:`Object ${p.object_key} deleted`};
    }));
  • Input schema for cos_delete_object: requires bucket_name (string), object_key (string), and optional region (string).
    server.tool("cos_delete_object", "Delete an object from a bucket", {
      bucket_name: z.string(), object_key: z.string(), region: z.string().optional(),
    }, async (p) => safeTool(async () => { w();
  • Tool registration via server.tool('cos_delete_object', ...) with description 'Delete an object from a bucket'.
    server.tool("cos_delete_object", "Delete an object from a bucket", {
  • src/server.ts:59-60 (registration)
    Indirect registration: registerCOSTools(server, client, config) is called from the server setup, which registers cos_delete_object among other COS tools.
    registerCOSTools(server, client, config);
    console.error(`  ✓ Cloud Object Storage (12 tools)`);
Behavior2/5

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

No annotations exist. The description does not disclose whether deletion is permanent, immutable, or if it triggers cascading effects. This is critical for a deletion operation.

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 sentence that is front-loaded with the key action and resource. However, it could be slightly more informative without losing conciseness.

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?

There is no output schema, no annotations, and the description lacks details on return behavior, error cases, or side effects. This is inadequate for a mutation tool.

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?

With 0% schema description coverage, the description should compensate. While parameter names are self-explanatory, the description adds no information beyond the schema, such as the role of 'region' or the format of 'object_key'.

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 ('Delete') and the resource ('an object from a bucket'). It is specific and distinct from sibling tools like cos_get_object or cos_put_object.

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, nor are there any preconditions (e.g., bucket must exist, object must not be needed elsewhere).

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