Skip to main content
Glama
Sign In
chuk-mcp-s3-bucket-manager

chuk-mcp-s3-bucket-manager

by chrishayuk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_bucket

Delete an S3 bucket by name. Use the force option to remove a non-empty bucket.

Instructions

Delete an S3 bucket

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_name": "<bucket_name>",
      "force": "<force>"
    },
    "name": "delete_bucket"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceYes
bucket_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the action ('delete'), making the destructive nature implicit but failing to disclose the 'force' parameter's effect (e.g., deleting non-empty buckets) or irreversibility.

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

Conciseness3/5

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

The description is a single concise sentence, but it under-specifies an operation that has a nontrivial parameter ('force'). It is not verbose, but the extreme brevity limits its usefulness.

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 lack of annotations, output schema, and schema descriptions, the tool description is insufficient. It doesn't mention error conditions, whether force is required for non-empty buckets, or any safety implications, making it incomplete for a destructive operation.

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 coverage is 0%, and the description does not explain any parameters. 'bucket_name' is self-evident from its name, but 'force' is a boolean with no explanation of its meaning or when to set it, leaving the agent without critical parameter understanding.

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 tool's purpose with a specific verb ('Delete') and resource ('an S3 bucket'), distinguishing it from sibling tools list_buckets and create_bucket.

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?

Usage is implied (use when you want to remove an S3 bucket) but no explicit context or alternatives are provided. It doesn't mention prerequisites like the bucket existing or being empty.

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

Deploy Server

Other Tools