Skip to main content
Glama

Delete object storage bucket

delete_object_storage_bucket
Destructive

Stop managing an object storage bucket in Ankra (the twin of ankra bucket delete). By default the bucket and every object in it stay on the provider and only the keys Ankra held are dropped. destroy_provider_resources=true also EMPTIES AND DELETES the bucket and removes what Ankra created for it - its data is gone for good. A bucket still provisioning is always torn down. Requires credentials.delete.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "bucket_id": "<bucket_id>"
    },
    "name": "delete_object_storage_bucket"
  }
}

Input Schema

NameRequiredDescriptionDefault
bucket_idYesObject storage bucket id (UUID) from list_object_storage_buckets.
destroy_provider_resourcesNotrue to empty and delete the bucket at the provider as well. Omit or false to keep the bucket and its data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, and the description goes well beyond that: it specifies exactly what is removed in each mode, that the default leaves provider data intact, that the destructive mode empties the bucket and the data is 'gone for good', and that it requires credentials.delete. This is precisely the operational context an agent needs before firing a destructive call.

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 destructive default/override distinction is front-loaded and every clause carries information. Capitalized emphasis on EMPTIES AND DELETES is slightly shouty and the CLI-twin parenthetical is decorative, but neither costs the reader meaningfully.

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

Completeness5/5

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

Covers the full decision surface for a two-parameter destructive tool: default behavior, override behavior, irreversibility, the provisioning edge case, and the required credential scope. With no output schema and complete schema descriptions, nothing an agent needs before calling is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns above that by explaining the consequence of omitting destroy_provider_resources versus setting it true ('EMPTIES AND DELETES the bucket and removes what Ankra created for it'), which is a semantic effect the schema only gestures at. bucket_id is left to the schema, which already documents it well.

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?

States a specific verb and resource ('Stop managing an object storage bucket in Ankra') and ties it to the CLI equivalent ('the twin of `ankra bucket delete`'), which disambiguates it from create_object_storage_bucket, get_object_storage_bucket, and list_object_storage_buckets. An agent can identify the operation without opening the schema.

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

Usage Guidelines4/5

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

Gives clear context on the default path (Ankra keys dropped, provider bucket and objects retained) versus the explicit destructive path with destroy_provider_resources=true, and adds the edge case that a bucket still provisioning is always torn down. It stops short of naming a sibling alternative or a prerequisite step (e.g., verify with get_object_storage_bucket first), which keeps it from a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.