@atengk/mcp-server-s3

create_bucket

Create a new S3-compatible storage bucket, optionally specifying a deployment region.

Instructions

创建新存储桶（支持指定部署区域）

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

Name	Required	Description	Default
`bucket`	Yes
`region`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 4, 2026

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 behavioral burden. It does not mention bucket-name global uniqueness, required permissions, whether creation is reversible, or any limits on bucket count — significant omissions 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.

Conciseness4/5

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

A single short sentence, front-loaded with the verb and resource, with the optional region capability in parentheses. It is efficient, though the terseness borders on under-specification.

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?

For a write operation with no annotations, no output schema, and 0% parameter documentation, the description is too thin. Critical details (name collision behavior, permission requirements, region default, return value) are absent.

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 0%, so the description must compensate. It loosely maps to both parameters, clarifying that 'region' means the deployment region, but adds no naming rules, format, or default behavior for either parameter.

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?

States a specific verb and resource ('create a new storage bucket') plus an optional capability (specifying the region). An agent can distinguish it from siblings like delete_bucket, list_buckets, or get_bucket_location, though no sibling is named explicitly.

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 offers no context on when to create a bucket versus when to use other tools, nor any prerequisites (credentials, permissions, namespace constraints). The only guidance is the parenthetical about region support.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.