Skip to main content
Glama

Scalix Cloud

by world.scalix

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesBucket name, unique within the project
publicNotrue = all objects publicly readable without auth; false (default) = private, share via presigned URLs

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 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"
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, and the description does not contradict these. It adds important behavioral traits beyond annotations: bucket names must be unique within the project, and setting public=true makes every object readable without authentication. These are crucial side effects that go beyond the binary hints.

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?

The description is two sentences, front-loaded with the primary purpose and followed by key details. Every sentence earns its place: the first states the action and object, the second explains uniqueness and public/private behavior. No redundant or wasted text.

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

Completeness5/5

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

For a simple two-parameter tool with no output schema, the description is complete. It covers the purpose, naming constraint, default behavior, and security implications. The annotations provide the safety profile, and the description covers the functional and contextual aspects needed for correct selection and invocation.

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 description coverage is 100%, so the baseline is 3. The description adds extra meaning for the 'public' parameter by explaining the default (false) and recommending presigned URLs for private sharing. This goes beyond the schema's field descriptions and clarifies the security implications.

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?

The description clearly states the verb and resource: 'Create a new Scalix Storage bucket in the project (S3-compatible object storage).' It is specific and distinguishes this tool from storage_upload/download/list by focusing on bucket creation. There is no sibling create_bucket tool, so the purpose is unambiguous.

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?

The description provides clear context on when to use the tool (creating a bucket) and gives practical guidance on public vs. private sharing, including the recommendation to use presigned URLs for private sharing. It does not explicitly name alternatives or exclusions, but no alternative create-bucket sibling exists, so the context is sufficient for proper usage.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation4/5

Tools are grouped by service prefix and generally target distinct resources/actions. A few execution surfaces could be confused (sandbox_run vs computer_exec vs fn_invoke; build_create vs fn_deploy vs run_deploy), and storage_list is overloaded for both buckets and objects, but descriptions clarify the boundaries well.

Naming Consistency4/5

The scalix_ prefix plus snake_case is used throughout, and most tools follow <service>_<verb>_<noun>. Minor deviations like scalix_search, scalix_status, and scalix_usage omit a service-domain qualifier, but the overall pattern is predictable and easy to navigate.

Tool Count2/5

53 tools is a very large surface. While the server covers a broad multi-service cloud platform, the count falls well beyond the 25+ threshold and will likely feel overwhelming; many service areas could reasonably be split into separate servers or trimmed.

Completeness2/5

Several service lifecycles have obvious gaps: the KV store has get/list/set but no delete, storage has upload/download/list but no delete for objects or buckets, functions have deploy/list/invoke but no delete/update, and cron has create but no list/delete. These missing operations create dead ends for agents managing common resources.

Resources