Skip to main content
Glama
zb-ss

Servonaut

by zb-ss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

s3_delete_object

Permanently delete a single S3 object across AWS, Hetzner, or OVH after confirming provider, bucket, and key; reserved for guard-mode and irreversible.

Instructions

Delete a single object from S3. Irreversible. Reserved for dangerous guard mode. ALWAYS confirm with the user (provider, bucket, key) before calling.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesObject key to delete.
bucketYesBucket name.
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 delivers the critical traits: irreversibility, a mode-based access gate, and a mandatory confirmation step naming the exact identifying parameters. It stops short of disclosing return/error behavior (e.g., missing key, versioned buckets).

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, front-loaded with the action, then the risk, then the gating requirement. Every sentence earns its place with zero 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 5-parameter tool with no annotations and no output schema, the description supplies purpose, risk, and safety workflow, which is most of what an agent needs. Remaining gaps (failure modes, response shape) are minor given the fully-described schema.

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%, so all five parameters are already documented, including the enum and the nuanced region/account semantics. The description only echoes (provider, bucket, key) as confirmation targets and adds no syntax or format detail beyond the schema, so the 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 and resource ('Delete a single object from S3'), and the word 'single object' distinguishes it from the sibling s3_delete_bucket and s3_delete_object's other list/upload siblings. 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 a clear gating condition ('Reserved for dangerous guard mode') and a required pre-call workflow ('ALWAYS confirm with the user (provider, bucket, key) before calling'). It does not explicitly name alternatives, but the when-to-use context is unambiguous.

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