Skip to main content
Glama
zb-ss

Servonaut

by zb-ss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

s3_delete_bucket

Delete an empty S3 bucket on AWS, Hetzner, or OVH. Fails if objects remain; irreversible, so confirm with the user before use.

Instructions

Delete an EMPTY S3 bucket. Operation fails if any object remains. Irreversible. Reserved for dangerous guard mode. ALWAYS confirm with the user before calling.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bucketYesBucket name to delete (must be empty).
regionNoRegion the bucket lives in (e.g. 'eu-central-1'). Omit unless you know it — it is resolved automatically. AWS, and OVH when no endpoint URL is configured (pass the region s3_list_buckets reports). Rejected for Hetzner, and for an OVH endpoint URL set by hand, whose region is fixed by that endpoint.
accountNoAccount label of the provider whose object storage to use; omit for that provider's default account.
providerYesStorage provider.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.28.0
    • addedInput schema / properties / account
      Added value: +{
+  "description": "Account label of the provider whose object storage to use; omit for that provider's default account.",
+  "type": "string"
+}
    • changedInput schema / properties / region / description
      Previous value: -"Region the bucket lives in (e.g. 'eu-central-1'). Omit unless you know it — it is resolved automatically. AWS only; rejected for Hetzner/OVH, whose region is fixed by the configured endpoint URL."New value: +"Region the bucket lives in (e.g. 'eu-central-1'). Omit unless you know it — it is resolved automatically. AWS, and OVH when no endpoint URL is configured (pass the region s3_list_buckets reports). Rejected for Hetzner, and for an OVH endpoint URL set by hand, whose region is fixed by that endpoint."
  2. Changed1 schema field changedv2.24.2
    • addedInput schema / properties / region
      Added value: +{
+  "description": "Region the bucket lives in (e.g. 'eu-central-1'). Omit unless you know it — it is resolved automatically. AWS only; rejected for Hetzner/OVH, whose region is fixed by the configured endpoint URL.",
+  "type": "string"
+}
  3. Addedv2.24.0
  4. Removedv2.23.8
  5. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the operation fails if objects remain, that it is irreversible, and that user confirmation is required. It omits permission requirements and rate/guard-mode mechanics, but the critical destructive-context traits are present.

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?

Four terse sentences, each front-loading the most important constraint (emptiness) before the irreversible and confirmation warnings. Zero wasted words.

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 destructive tool with no annotations and no output schema, the description covers the essential safety profile (empty precondition, irreversibility, confirmation). It could add what the response reports on success/failure, but is largely sufficient.

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 description coverage is 100%, so the schema fully documents bucket, region, account, and provider. The description adds only the emptiness constraint (already implied in the schema), so baseline 3 applies.

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 (Delete) and resource (EMPTY S3 bucket) and immediately names the defining constraint: the bucket must be empty. This clearly distinguishes it from siblings like s3_delete_object (deletes objects) and s3_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 Guidelines4/5

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

Gives clear preconditions (bucket must be empty, reserved for dangerous guard mode) and an explicit instruction to confirm with the user. It does not name an alternative path (e.g., emptying via s3_delete_object first), so it stops short of full routing guidance.

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