Skip to main content
Glama

list_buckets

Retrieve available storage buckets from Huawei OBS, including names, creation dates, and locations, for managing cloud object storage resources.

Instructions

List all storage buckets available in the 'huawei_obs' source. Returns bucket names, creation dates, and locations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The async handler function for the list_buckets tool, which currently returns a placeholder response indicating implementation is pending. Uses closure variables sourceId and storage.endpoint from the registration loop.
    async () => {
      // TODO: Implement actual bucket listing with storage provider
      return createToolSuccessResponse({
        message: `Bucket listing from '${sourceId}' not yet implemented`,
        source_id: sourceId,
        endpoint: storage.endpoint,
        note: "Storage provider integration pending",
      });
    }
  • src/server.ts:166-179 (registration)
    Registration of the list_buckets tool using McpServer.tool(), dynamically suffixed per storage source. Includes description, empty Zod input schema, and inline handler.
    server.tool(
      `list_buckets${toolSuffix}`,
      `List all storage buckets available in the '${sourceId}' source. Returns bucket names, creation dates, and locations.`,
      {},
      async () => {
        // TODO: Implement actual bucket listing with storage provider
        return createToolSuccessResponse({
          message: `Bucket listing from '${sourceId}' not yet implemented`,
          source_id: sourceId,
          endpoint: storage.endpoint,
          note: "Storage provider integration pending",
        });
      }
    );
  • TypeScript interface defining ListBucketsToolConfig for configuration of list_buckets tool in TOML files (though built-in tools are hardcoded).
     * Built-in storage tool configuration for list_buckets
     */
    export interface ListBucketsToolConfig {
      name: "list_buckets";
      source: string;
    }
  • Constant array of built-in storage tool names, including "list_buckets", used for validation and checks.
    export const BUILTIN_STORAGE_TOOLS = [
      "list_buckets",
      "list_objects",
      "get_object",
      "get_object_metadata",
      "search_objects",
    ] as const;
  • src/server.ts:288-288 (registration)
    Console log confirming successful registration of the list_buckets tool.
    console.error(`  - list_buckets${toolSuffix} registered`);
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses the return format (bucket names, creation dates, and locations) which is valuable behavioral information. However, it doesn't mention pagination behavior, rate limits, authentication requirements, or error conditions that would be important for a list operation.

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 perfectly concise with two sentences that each earn their place. The first sentence states the action and scope, the second describes the return format. No wasted words or redundant information.

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?

For a simple list operation with 0 parameters and no output schema, the description provides good context about what's returned. However, without annotations and with no output schema, it could benefit from more detail about response format structure, pagination, or error handling to be fully complete.

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 has 0 parameters with 100% schema description coverage, so the baseline would be 4. The description appropriately doesn't discuss parameters since none exist, and instead focuses on what the tool does and returns.

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 specific action ('List all storage buckets'), identifies the resource ('storage buckets'), and specifies the scope ('available in the 'huawei_obs' source'). It also distinguishes from siblings by focusing on buckets rather than objects or SQL operations.

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?

The description implies usage context by specifying the 'huawei_obs' source, but doesn't explicitly state when to use this tool versus alternatives like list_objects or search_objects. No explicit exclusions or alternative recommendations are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zq940222/hybrid-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server