Skip to main content
Glama

Get object storage bucket

get_object_storage_bucket
Read-only

Show one object storage bucket: provider, region, bucket name, endpoint, the credential it was created with, status and error excerpt. Key material is never returned. Discover bucket ids with list_object_storage_buckets. Read-only.

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": {
      "bucket_id": "<bucket_id>"
    },
    "name": "get_object_storage_bucket"
  }
}

Input Schema

NameRequiredDescriptionDefault
bucket_idYesObject storage bucket id (UUID) from list_object_storage_buckets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is known; the description adds substantive context beyond that by enumerating the fields returned and, importantly, promising that key material is never returned. It does not discuss error behavior when the bucket id is unknown, but the security guarantee is a meaningful addition.

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?

Two short sentences, front-loaded with what is returned and followed by the discovery path and safety note. Nothing is redundant apart from a mildly duplicative 'Read-only' that mirrors the annotation.

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 single-parameter read tool with no output schema, the description covers what the response contains, how to obtain the required id, and what is deliberately excluded. An agent has everything needed to call it correctly.

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 description coverage is 100% and the single parameter is documented as a UUID obtained from list_object_storage_buckets. The description reinforces that provenance but adds no format or validation detail beyond the schema, so the baseline 3 applies.

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 states a specific verb ('Show one') and resource ('object storage bucket'), then enumerates the returned fields (provider, region, bucket name, endpoint, credential, status, error excerpt). This clearly differentiates it from list_object_storage_buckets and from create/delete_object_storage_bucket siblings.

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?

It explicitly routes the agent to list_object_storage_buckets to discover a bucket id, which is the practical precondition for calling this tool, and labels the operation read-only. It does not state when the detail view is unnecessary versus other inspection tools, but the context is clear enough.

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.