Skip to main content
Glama
Sign In
s3-mcp

s3-mcp

by JakePeralta7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_bucket

Create a new S3 bucket in the configured region to organize and store your objects.

Instructions

Create a bucket in the configured region.

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": "<bucket>"
    },
    "name": "create_bucket"
  }
}

Input Schema

NameRequiredDescriptionDefault
bucketYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only mentions that the bucket is created in the configured region; it does not mention permissions, idempotency, failure behavior, or side effects of creating a bucket.

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 a single, front-loaded sentence with no filler. Every word contributes to the meaning, and it is appropriately sized for a one-parameter tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one required string parameter and an output schema, this is minimally viable. However, it lacks any usage context or behavioral caveats, so it is not particularly helpful to an agent deciding how or when to invoke it.

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?

Schema description coverage is 0%, and the description does not explain the 'bucket' parameter beyond the fact that a bucket is being created. It adds little on top of the parameter name and type, leaving format and constraints undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear action ('Create') and a clear resource ('bucket'), and adds the qualifier 'in the configured region.' This distinguishes it from sibling tools like delete_bucket or list_buckets, though it relies partly on the tool name and sibling context to do so.

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 about when to use this tool instead of alternatives, no prerequisites or exclusions, and no mention of behavior when the bucket already exists. The use case is implied by the verb but never made explicit.

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