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

chuk-mcp-s3-bucket-manager

by chrishayuk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create_bucket

Create a new Amazon S3 bucket with a specified bucket name. Use this tool to set up storage for your objects and files.

Instructions

Create a new 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>"
    },
    "name": "create_bucket"
  }
}

Input Schema

NameRequiredDescriptionDefault
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 exist to declare safety or mutation, and the description adds no behavioral context such as idempotency, permission needs, failure modes, or side effects. 'Create' implies mutation but nothing more.

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

Conciseness4/5

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

The description is a single, front-loaded sentence with no waste. It is concise, though it could have used the space to add useful detail without becoming verbose.

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?

With no output schema or annotations, the description should at least mention what happens on success or important constraints. It provides none, making it insufficient for an agent to fully understand invocation outcomes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage, and the description does not explain bucket_name semantics (e.g., naming rules, uniqueness, format). It merely repeats the action without adding value beyond the raw parameter name.

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 uses the specific verb 'Create' with the resource 'S3 bucket', clearly identifying the tool's action. It distinguishes from siblings list_buckets and delete_bucket by the action verb.

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?

There is no guidance on when to use this tool versus alternatives. No prerequisites, context, or exclusions are provided; the description only states the basic action.

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