Skip to main content
Glama
pickstar-2002

MinIO Storage MCP

list_buckets

Retrieve all storage buckets from MinIO object storage to view available containers for data management and organization.

Instructions

列出所有存储桶

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'list_buckets': calls minioClient.listBuckets() and returns formatted text response with bucket names and creation dates.
    case 'list_buckets': {
      const buckets = await this.minioClient.listBuckets();
      return {
        content: [
          {
            type: 'text',
            text: `找到 ${buckets.length} 个存储桶:\n${buckets.map(b => `- ${b.name} (创建时间: ${b.creationDate.toISOString()})`).join('\n')}`
          }
        ]
      };
    }
  • src/index.ts:83-86 (registration)
    Registration of the 'list_buckets' tool in the ListTools response, including name, description, and empty input schema.
    {
      name: 'list_buckets',
      description: '列出所有存储桶',
      inputSchema: { type: 'object', properties: {} }
  • Core implementation of listBuckets in MinIOStorageClient: ensures connection, lists buckets via MinIO client, maps to BucketInfo array.
    async listBuckets(): Promise<BucketInfo[]> {
      this.ensureConnected();
      const buckets = await this.client!.listBuckets();
      return buckets.map((bucket: any) => ({
        name: bucket.name,
        creationDate: bucket.creationDate
      }));
    }
  • Type definition for BucketInfo used in listBuckets return type.
    export interface BucketInfo {
      name: string;
      creationDate: Date;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the action ('列出' - list) but doesn't disclose behavioral traits such as whether it requires authentication, if it's read-only (implied but not stated), rate limits, pagination behavior, error conditions, or what the output format looks like. For a tool with zero annotation coverage, this leaves significant gaps.

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 phrase ('列出所有存储桶') that directly states the tool's purpose with zero wasted words. It's appropriately sized and front-loaded, making it easy to understand at a glance.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters) but lack of annotations and output schema, the description is incomplete. It doesn't explain what the output contains (e.g., bucket names, metadata), potential errors, or behavioral context like authentication needs. For a list operation with no structured output documentation, more detail would be helpful.

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 input schema has 0 parameters with 100% coverage, so the schema fully documents the absence of parameters. The description doesn't need to add parameter details, and it correctly implies no inputs are required by not mentioning any. This meets the baseline for tools with no parameters.

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 '列出所有存储桶' (List all storage buckets) clearly states the tool's purpose with a specific verb ('列出' - list) and resource ('存储桶' - storage buckets). It distinguishes itself from siblings like 'bucket_exists' (checks existence) and 'list_objects' (lists objects within a bucket), but doesn't explicitly mention these distinctions in the description itself.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing to connect first), when it's appropriate (e.g., for inventory checks), or when to choose other tools like 'get_storage_stats' for metrics or 'bucket_exists' for existence verification.

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/pickstar-2002/minio-storage-mcp'

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