Skip to main content
Glama
hostkey-cloud

hostkey-mcp-server

Official
by hostkey-cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

s3_delete_bucket

Destructive

Permanently deletes an S3 bucket and all its files; requires explicit confirmation to prevent accidental data loss.

Instructions

Delete a bucket from an S3 account (s3/delete_bucket). DESTRUCTIVE: all files in the bucket will be deleted.

Input Schema

NameRequiredDescriptionDefault
s3uidNoS3 account UID; omit only if the token is bound to a single S3 account
bucketYesBucket name
confirmYesMust be true to run the operation.
account_idNoDeprecated alias for s3uid / get_users.id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.8
    • changedInput schema / properties / account_id / description
      Previous value: -"Deprecated alias for s3uid"New value: +"Deprecated alias for s3uid / get_users.id"
  2. Changed2 schema fields changedv1.0.4
    • changedInput schema / properties / account_id / description
      Previous value: -"S3 account ID (if required; check via s3_get_users)"New value: +"Deprecated alias for s3uid"
    • addedInput schema / properties / s3uid
      Added value: +{
+  "description": "S3 account UID; omit only if the token is bound to a single S3 account",
+  "type": [
+    "string",
+    "number"
+  ]
+}
  3. Changed2 schema fields changedv1.0.3
    • changedInput schema / properties / account_id / description
      Previous value: -"ID S3-аккаунта (если требуется; уточняйте через s3_get_users)"New value: +"S3 account ID (if required; check via s3_get_users)"
    • changedInput schema / properties / bucket / description
      Previous value: -"Имя бакета"New value: +"Bucket name"
  4. First observedv1.0.1

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=false, openWorldHint=true, and destructiveHint=true, so the safety profile is covered. The description adds valuable context by stating the concrete consequence: 'all files in the bucket will be deleted'. However, it does not mention the required confirmation flag or irreversibility beyond that consequence.

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?

The description is two short sentences and is front-loaded with the core action. Every sentence adds useful information: the first states purpose and API path, the second states the destructive consequence. There is no filler.

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 full annotation coverage (destructiveHint=true), a fully documented schema, and no output schema, the description provides the essential warning that all files are deleted. It could be slightly more complete by mentioning the confirm=true requirement explicitly, but the schema already documents that parameter.

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 all four parameters are fully documented in the schema itself. The description adds no parameter-level meaning beyond what is already in the schema, which is acceptable given the high coverage.

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 states a specific verb and resource: 'Delete a bucket from an S3 account'. It also includes the underlying API operation path. Because it explicitly names the bucket as the target, it is inherently distinguishable from sibling operations like s3_delete_file and s3_delete_account.

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?

The description does not explain when to use this tool versus alternatives such as s3_delete_file, s3_delete_account, or s3_delete_bucket-like operations. It also does not mention prerequisites like the required confirm=true flag, though that is documented in the schema. It merely implies usage through the tool name and purpose.

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