Skip to main content
Glama
zb-ss

Servonaut

by zb-ss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

s3_create_bucket

Create a new S3 bucket on AWS, Hetzner, or OVH; confirm provider, bucket name, and region first because billing starts immediately.

Instructions

Create a new S3 bucket on the given provider. Costs money — billing starts immediately. Reserved for dangerous guard mode. Confirm with the user (provider, bucket name, region) before calling.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bucketYesBucket name to create.
regionNoRegion to create the bucket in (e.g. 'eu-central-1'). Omit to use the configured region for the provider. AWS, and OVH when no endpoint URL is configured. For Hetzner, or an OVH endpoint URL set by hand, the region is fixed by that endpoint and an override is rejected.
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 to create the bucket in (e.g. 'eu-central-1'). Omit to use the configured region for the provider. AWS only — for Hetzner/OVH the region is fixed by the configured endpoint URL and an override is rejected."New value: +"Region to create the bucket in (e.g. 'eu-central-1'). Omit to use the configured region for the provider. AWS, and OVH when no endpoint URL is configured. For Hetzner, or an OVH endpoint URL set by hand, the region is fixed by that endpoint and an override is rejected."
  2. Changed1 schema field changedv2.24.2
    • addedInput schema / properties / region
      Added value: +{
+  "description": "Region to create the bucket in (e.g. 'eu-central-1'). Omit to use the configured region for the provider. AWS only — for Hetzner/OVH the region is fixed by the configured endpoint URL and an override is rejected.",
+  "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 provided, the description carries the full burden and does well: it discloses the cost side effect ('Costs money — billing starts immediately'), the guard-mode gating, and the required user confirmation. It omits idempotency/naming-failure behavior and permission requirements, so it is strong but not exhaustive for a mutation tool.

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 with zero filler, front-loading the action, then the cost/guard implications, then the required confirmation. Every sentence earns its place.

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 mutating tool with no annotations and no output schema, the description covers the critical behavioral facts an agent needs (cost, guard mode, user confirmation). Remaining gaps — failure/idempotency behavior and permissions — are minor but prevent a 5.

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 already documents all four parameters, including region override behavior and account defaults. The description only names three of them in the confirmation list and adds no syntax or format detail beyond the schema. Baseline 3 is appropriate.

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 ('Create a new S3 bucket') and adds scope ('on the given provider'), which cleanly distinguishes it from siblings like s3_list_buckets, s3_delete_bucket, and s3_upload_object without needing to open any 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?

It gives concrete preconditions: 'Reserved for dangerous guard mode' and 'Confirm with the user (provider, bucket name, region) before calling.' This tells the agent when this tool is permitted and what must happen first. It does not explicitly name alternative tools, but the 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