Skip to main content
Glama

List object storage buckets

list_object_storage_buckets
Read-only

List the organisation's object storage buckets Ankra created on its provider credentials (the twin of ankra bucket list): name, provider, region, provider-side bucket name, endpoint, status and error excerpt. Key material is never returned. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_object_storage_buckets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and the description confirms "Read-only." Beyond that it adds a genuine security-relevant disclosure: "Key material is never returned," which matters for a tool listing storage buckets. It also enumerates the returned fields, compensating for the missing output schema; pagination and result ordering remain undisclosed.

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?

One dense front-loaded sentence plus two short clauses; the scope constraint and field list come before the caveats. The parenthetical CLI twin ("the twin of `ankra bucket list`") is arguably filler for an agent that never invokes the CLI, but it is a minor cost.

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 wisely enumerates the returned fields, and with no parameters there is nothing else to document. The remaining gap is operational: nothing says whether results are paginated, limited, or ordered, which matters for an org-wide listing that could be large.

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?

The tool takes zero parameters, so the schema imposes no documentation burden and the baseline is 4. The description correctly adds nothing about arguments and instead spends its words on scope and output, which is the right allocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List the organisation's object storage buckets") plus a meaningful scope qualifier: buckets Ankra created on its own provider credentials. The enumeration of returned fields further pins down what the listing is. It stops short of naming the sibling get_object_storage_bucket as the single-bucket alternative, so differentiation is implicit rather than explicit.

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

Usage Guidelines3/5

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

Usage is implied by the scoping (organisation-wide, Ankra-managed buckets only) rather than stated. There is no explicit "use this when..." guidance and no exclusion pointing to get_object_storage_bucket for detail or create/delete_object_storage_bucket for mutations. An agent can infer the context but must do the routing work itself.

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.