Skip to main content
Glama
pickstar-2002

MinIO Storage MCP

create_bucket

Create storage buckets in MinIO object storage to organize and manage data. Specify bucket name and optional region for structured data storage.

Instructions

创建存储桶

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bucketNameYes存储桶名称
regionNo区域设置(可选)

Implementation Reference

  • Handler for the 'create_bucket' tool. Parses arguments using Zod, calls minioClient.createBucket, and returns a success message.
    case 'create_bucket': {
      const { bucketName, region } = z.object({
        bucketName: z.string(),
        region: z.string().optional()
      }).parse(args);
      
      await this.minioClient.createBucket(bucketName, region);
      return {
        content: [
          {
            type: 'text',
            text: `成功创建存储桶: ${bucketName}`
          }
        ]
      };
    }
  • src/index.ts:88-99 (registration)
    Registration of the 'create_bucket' tool in the list_tools response, including name, description, and input schema.
    {
      name: 'create_bucket',
      description: '创建存储桶',
      inputSchema: {
        type: 'object',
        properties: {
          bucketName: { type: 'string', description: '存储桶名称' },
          region: { type: 'string', description: '区域设置(可选)' }
        },
        required: ['bucketName']
      }
    },
  • Zod schema validation for create_bucket inputs within the handler.
    const { bucketName, region } = z.object({
      bucketName: z.string(),
      region: z.string().optional()
    }).parse(args);
  • Helper method in MinIOStorageClient that performs the actual bucket creation using the MinIO client's makeBucket method.
    async createBucket(bucketName: string, region?: string): Promise<void> {
      this.ensureConnected();
      await this.client!.makeBucket(bucketName, region || this.config!.region || 'us-east-1');
    }
Behavior1/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 of behavioral disclosure. It only states the action ('create') without any details on permissions required, whether the operation is idempotent, error conditions (e.g., duplicate bucket names), rate limits, or what happens on success/failure. This is inadequate for a mutation tool with zero annotation coverage.

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 extremely concise with a single phrase ('创建存储桶'), which is front-loaded and wastes no words. However, this conciseness comes at the cost of completeness, but based solely on brevity and structure, it earns full marks.

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

Completeness1/5

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

Given the complexity of a creation tool with no annotations and no output schema, the description is severely incomplete. It lacks essential context such as what the tool returns, error handling, dependencies on other tools (e.g., 'connect_minio'), and behavioral traits. This makes it inadequate for safe and effective use by an AI agent.

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?

The schema description coverage is 100%, with clear descriptions for both parameters ('bucketName' and optional 'region'). The description adds no additional meaning beyond what the schema provides, such as format constraints or examples. Given the high schema coverage, the baseline score of 3 is appropriate as the schema handles the parameter documentation adequately.

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

Purpose2/5

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

The description '创建存储桶' (Create storage bucket) restates the tool name 'create_bucket' in Chinese, making it essentially tautological. While it indicates a creation action and resource type, it doesn't specify what distinguishes this from other bucket-related tools like 'set_bucket_policy' or 'delete_bucket' beyond the basic verb.

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

Usage Guidelines1/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 a connection via 'connect_minio'), exclusions (e.g., not for existing buckets), or comparisons with sibling tools like 'list_buckets' or 'bucket_exists'.

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