Skip to main content
Glama

Create object storage bucket

create_object_storage_bucket
Destructive

Create an object storage bucket on one of the organisation's provider credentials - Hetzner, Scaleway, DigitalOcean or UpCloud (the twin of ankra bucket create). Ankra creates and verifies the bucket in the background and keeps its keys; get_object_storage_bucket reports ready or error once it finishes. No keys travel here: a Hetzner bucket needs the Object Storage key pair already stored on the Hetzner credential. Requires credentials.write.

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>",
      "credential_id": "<credential_id>",
      "region": "<region>"
    },
    "name": "create_object_storage_bucket"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe bucket's name in Ankra: a lowercase label such as registry-storage, unique in the organisation.
bucketNoProvider-side bucket name to create; omit to let Ankra derive a unique one from the name.
regionYesProvider region: fsn1/nbg1/hel1 (Hetzner), fr-par/nl-ams/pl-waw (Scaleway), fra1/nyc3/... (DigitalOcean) or europe-1/us-1 (UpCloud).
credential_idYesUUID of the provider credential (from list_credentials) the bucket is created with; its provider decides where.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: creation and verification happen in the background, Ankra retains the keys, no key material is transmitted, and Hetzner requires a pre-stored key pair on the credential. It does not explain why destructiveHint=true or what happens to a half-created bucket on verification failure, which would have closed the loop.

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?

Front-loaded with the action and provider list, then prerequisites and lifecycle. Dense but every sentence carries information; the parenthetical CLI alias is the only line that serves less purpose for an agent.

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

Completeness4/5

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

No output schema, but the description compensates by naming the follow-up tool that reports ready/error. Prerequisites, permissions, provider scope and async behavior are all covered; only failure/rollback semantics are left implicit.

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 coverage is 100%, so the baseline is 3. The description does add one genuinely extra constraint absent from the schema — that the credential's provider determines where the bucket lands, and that region/provider must therefore align — but it says nothing about the name-vs-bucket relationship or region defaults.

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?

Specific verb+resource ("Create an object storage bucket") with the exact provider set enumerated (Hetzner, Scaleway, DigitalOcean, UpCloud), plus a CLI equivalent and a named sibling for follow-up status. An agent can distinguish this from list_object_storage_buckets, get_object_storage_bucket and delete_object_storage_bucket from the text alone.

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

Usage Guidelines4/5

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

States the prerequisite ("Requires credentials.write"), the async lifecycle, and routes to get_object_storage_bucket for completion polling. Missing an explicit negative case — e.g. when to skip this and reuse an existing bucket, or how it relates to list_object_storage_buckets for duplicate checks.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.