List storage buckets, or list objects in a specific bucket with optional prefix filter.
| Name | Required | Description | Default |
|---|---|---|---|
| bucket | No | Bucket name. If omitted, lists all buckets. | |
| prefix | No | Filter objects by key prefix |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering safety. The description adds the dual-mode behavior and prefix filtering, which is useful but doesn't disclose response format, pagination, or other operational details.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no wasted words. It efficiently communicates the tool's core behavior.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With two optional parameters fully described in the schema and annotations covering safety, the description sufficiently defines the tool's scope. It doesn't explain return values, but this is a simple list operation and no output schema exists.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents both parameters. The description's mention of 'optional prefix filter' adds no new semantics beyond the schema's 'Filter objects by key prefix'.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action (list), the resource (storage buckets/objects), and distinguishes between two modes: listing all buckets vs. objects in a specific bucket. This differentiates it from sibling tools like storage_upload and storage_download.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use it: without bucket for all buckets, with bucket for objects. It also mentions the optional prefix filter. It doesn't explicitly exclude alternatives, but the context is clear given the tool's role.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.
