Skip to main content
Glama
akave-ai

Akave MCP Server

by akave-ai

list_buckets

Retrieve a complete list of all storage buckets available in your Akave S3-compatible storage account for management and organization purposes.

Instructions

List all buckets in Akave storage

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/server.ts:43-62 (registration)
    Registration of the 'list_buckets' MCP tool. Includes inline handler function that calls s3Client.listBuckets() and formats the response as JSON text content.
    this.server.tool(
      "list_buckets",
      "List all buckets in Akave storage",
      async () => {
        const buckets = await this.s3Client.listBuckets();
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(
                buckets.map((bucket) => ({
                  name: bucket.Name,
                  creationDate: bucket.CreationDate,
                }))
              ),
            },
          ],
        };
      }
    );
  • Inline handler function for 'list_buckets' tool: fetches buckets from S3 client and returns formatted list as tool response.
    async () => {
      const buckets = await this.s3Client.listBuckets();
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(
              buckets.map((bucket) => ({
                name: bucket.Name,
                creationDate: bucket.CreationDate,
              }))
            ),
          },
        ],
      };
    }
  • S3 client helper method that executes ListBucketsCommand and returns the buckets array.
    async listBuckets() {
      const command = new ListBucketsCommand({});
      const response = await this.client.send(command);
      return response.Buckets || [];
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states what the tool does but doesn't describe important behavioral traits like whether this requires authentication, how results are returned (pagination, format), rate limits, or error conditions. The description is minimal and lacks operational context.

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 a single, efficient sentence that states exactly what the tool does with zero wasted words. It's appropriately sized for a simple list operation and is front-loaded with the core functionality.

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

Completeness3/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 the basic purpose but lacks important context. Without annotations or output schema, the description should ideally mention what information is returned about buckets and any operational considerations, but it doesn't. It's minimally adequate but has clear gaps.

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 is 4. The description appropriately doesn't discuss parameters since none exist, and it doesn't need to compensate for any schema coverage gaps.

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?

The description clearly states the action ('List') and resource ('all buckets in Akave storage'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'list_objects' or 'list_object_versions', which would require mentioning it's specifically for buckets rather than objects.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives. The description doesn't mention prerequisites, when this should be used instead of other bucket-related tools like 'create_bucket' or 'get_bucket_location', or any context about typical usage patterns.

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/akave-ai/akave-mcp'

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