Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Cloudflare: Create r2 bucket

cloudflare_create_r2_bucket

Create a Cloudflare R2 bucket by specifying a site and a valid 3–63 character bucket name, enabling object storage setup for the account.

Instructions

[UNIFIED] Create an R2 bucket (requires R2 edit permission). Bucket names must be 3-63 lowercase letters, digits and hyphens, starting/ending with a letter or digit, unique within the account.

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": {
      "site": "<site>",
      "bucket_name": "<bucket_name>"
    },
    "name": "cloudflare_create_r2_bucket"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
account_idNo
bucket_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the mutation profile is covered structurally. The description adds genuinely useful behavior context — the permission requirement and the fact that names must be unique within the account — but does not state the failure mode on a duplicate name, which matters for a non-idempotent create.

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?

Two tightly packed sentences, front-loaded with the action and followed by the operational constraints. No filler and nothing repeated from the title.

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?

With no output schema and only minimal annotations, the description should be doing more work. It covers permissions and naming well but omits the semantics of the required 'site' parameter and the create-failure behavior, leaving real gaps for a three-parameter mutation tool.

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%, so the description carries the full burden, and it only explains one of three parameters. It gives detailed validation rules for bucket_name but leaves the required 'site' parameter and the optional 'account_id' completely unexplained, so an agent cannot tell what 'site' means or when to supply account_id.

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 names a specific verb and resource ('Create an R2 bucket') and immediately scopes it to R2, which cleanly separates it from the sibling delete/get/list R2 bucket tools. It stops short of naming an alternative explicitly, so it is clear but not maximally differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It supplies a prerequisite ('requires R2 edit permission') and the naming constraints needed for a successful call, which implies when the tool can be used. There is no explicit when-to-use versus when-not guidance, and no mention of what to do if the bucket already exists.

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