Edge Network

edge_create_bucket

Create an object storage bucket (S3-compatible). Free tier includes a limited number of buckets.

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": {
      "name": "<name>"
    },
    "name": "edge_create_bucket"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Bucket name: 3-63 chars, lowercase letters, numbers, hyphens
`dry_run`	No	Preview the action without executing it. Returns what would happen, including cost estimates. Always dry-run first for anything that costs money.

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 23, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. 'Create' clearly signals a state-changing mutation, and the free-tier note adds quota context. However, it does not disclose cost implications (despite the dry_run schema hint about cost estimates), idempotency, duplicate-name behavior, or what happens when the free-tier limit is exhausted.

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 sentences with zero filler; the core purpose is front-loaded, and the free-tier constraint is the only supporting detail, earning its place as a quota warning. Nothing extraneous is present.

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?

Adequate for a simple two-parameter tool with 100% schema coverage and no output schema. However, with no annotations, the description alone does not fully inform the agent about cost-sensitive behavior, success/failure responses, or quota-exceeded handling. The dry_run guidance in the schema partially compensates for these gaps.

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%; both parameters are fully documented in the schema, with name format rules and dry_run semantics including cost estimates. The description adds no additional parameter-level meaning beyond the S3-compatible context. Baseline 3 applies because the schema does the heavy lifting.

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?

States a specific verb ('Create') and a specific resource ('object storage bucket (S3-compatible)'). The S3-compatible qualifier clearly distinguishes it from siblings such as edge_create_dns_zone, edge_create_shield_widget, and edge_create_assist_site. An agent can identify the tool's function without opening the schema.

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?

No explicit guidance on when to use this tool versus alternatives. The free-tier note implies a quota constraint but does not instruct the agent to check edge_list_buckets first, use dry_run for cost-sensitive scenarios, or avoid creating buckets when the limit is near. No when-not-to-use or alternative routing is provided.

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

All Edge Network tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?