Skip to main content
Glama

Scalix Cloud

by world.scalix
OverviewDiscussionsAdmin

scalix_storage_create_bucket

Idempotent

Create a new Scalix Storage bucket in the project (S3-compatible object storage). Bucket names must be unique within the project. Setting public=true makes every object in the bucket readable without authentication — leave it false (the default) and use presigned URLs for private sharing. Public buckets double as static websites: upload index.html and serve it from the project's store subdomain at https://{slug}.store.scalix.world/buckets/{bucket}/objects/ (directory requests serve index.html; a 404.html object is served as the error page).

Input Schema

NameRequiredDescriptionDefault
nameYesBucket name, unique within the project (aliases: bucket)
bucketNoAlias of name — accepted for symmetry with the object tools
publicNotrue = all objects publicly readable without auth (also serves as a static website on {slug}.store.scalix.world); false (default) = private, share via presigned URLs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / bucket
      Added value: +{
+  "description": "Alias of name — accepted for symmetry with the object tools",
+  "type": "string"
+}
    • changedInput schema / properties / name / description
      Previous value: -"Bucket name, unique within the project"New value: +"Bucket name, unique within the project (aliases: bucket)"
  2. Changed1 schema field changed
    • changedInput schema / properties / public / description
      Previous value: -"true = all objects publicly readable without auth; false (default) = private, share via presigned URLs"New value: +"true = all objects publicly readable without auth (also serves as a static website on {slug}.store.scalix.world); false (default) = private, share via presigned URLs"
  3. Changed2 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"Bucket name"New value: +"Bucket name, unique within the project"
    • changedInput schema / properties / public / description
      Previous value: -"Whether the bucket is publicly accessible"New value: +"true = all objects publicly readable without auth; false (default) = private, share via presigned URLs"
  4. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true), and the description adds materially beyond them: the security consequence of public=true (every object readable without auth), the uniqueness constraint on names, and the static-website serving behavior. These are non-obvious behavioral traits an agent must know before calling.

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 core action, then constraints, then the public semantics. The static-website sentence is long and detail-heavy but genuinely useful; nothing is wasted, though it could be tightened.

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?

With no output schema, the description does not need to explain return values, and annotations cover safety. It fully covers creation behavior, naming uniqueness, and the public flag's implications. Minor gaps remain (e.g., naming rules, quota/limits), keeping it from a 5.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, but the description adds real meaning beyond the schema: it explains the default value and the operational consequences of public (auth-free reads, static website hosting, index.html/404.html semantics). It adds little for the name/bucket alias, but the public parameter is well served.

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+resource ('Create a new Scalix Storage bucket') and parenthetically clarifies the domain ('S3-compatible object storage'). This clearly separates it from siblings like scalix_storage_delete_bucket, scalix_storage_upload, and scalix_storage_list without the agent needing to open any schema.

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?

Gives explicit conditional guidance: leave public=false (the default) and use presigned URLs for private sharing, or set public=true for public/static-website use. It does not name a sibling tool as the alternative for private sharing (presigned URL generation is only implied), so it falls short of a 5.

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

All Scalix Cloud toolsInspect
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