Skip to main content
Glama

Delete a Sixteen Bridges bucket

sixteenbridges_delete_bucket
DestructiveIdempotent

Delete a Sixteen Bridges bucket. Its bubbles stay, in no bucket; none are deleted. Ask the user first.

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": "<bucket>"
    },
    "name": "sixteenbridges_delete_bucket"
  }
}

Input Schema

NameRequiredDescriptionDefault
bucketYesThe bucket's name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description earns credit for adding the non-obvious side effect: bubbles survive in an unbucketed state and none are deleted. It stops short of saying whether the bucket deletion is reversible or whether an empty bucket is required.

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?

Three short sentences, action first, side effect second, safety instruction last. Every clause carries information an agent needs and nothing is padded.

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

Completeness4/5

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

For a one-parameter destructive tool with rich annotations, the essentials are covered: what it deletes, what survives, and that user confirmation is required. Missing only edge-case behavior such as whether deleting a non-empty bucket is allowed or how bubbles are later recovered.

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

Parameters3/5

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

Schema coverage is 100% and the single `bucket` parameter is fully documented in the schema, so the description adds no format, matching, or lookup detail. Baseline 3 applies when the schema carries the semantics.

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?

Specific verb (Delete) plus resource (a Sixteen Bridges bucket), immediately distinguishable from the sibling delete_bubble. The added note that bubbles are not deleted further separates it from any operation on bubbles themselves.

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

Usage Guidelines3/5

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

'Ask the user first' gives a real precondition for invoking it, which is more than nothing. But it offers no explicit when-not guidance or comparison to update_bucket/move_bubbles for a user who just wants to empty or reorganize a bucket.

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.

Resources