Skip to main content
Glama
pickstar-2002

MinIO Storage MCP

copy_object

Copy objects between buckets in MinIO storage. Specify source and destination buckets with object names to duplicate files.

Instructions

复制对象

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceBucketYes源存储桶名称
sourceObjectYes源对象名称
destBucketYes目标存储桶名称
destObjectYes目标对象名称

Implementation Reference

  • The primary handler function that executes the object copy operation using the MinIO client's copyObject method.
    async copyObject(sourceBucket: string, sourceObject: string, destBucket: string, destObject: string): Promise<void> {
      this.ensureConnected();
      
      const copyConditions = new Minio.CopyConditions();
      await this.client!.copyObject(destBucket, destObject, `/${sourceBucket}/${sourceObject}`, copyConditions);
    }
  • Tool dispatcher in the CallToolRequest handler that validates input with Zod and calls the MinIO client handler.
    case 'copy_object': {
      const { sourceBucket, sourceObject, destBucket, destObject } = z.object({
        sourceBucket: z.string(),
        sourceObject: z.string(),
        destBucket: z.string(),
        destObject: z.string()
      }).parse(args);
      
      await this.minioClient.copyObject(sourceBucket, sourceObject, destBucket, destObject);
      return {
        content: [
          {
            type: 'text',
            text: `成功复制对象从 ${sourceBucket}/${sourceObject} 到 ${destBucket}/${destObject}`
          }
        ]
      };
    }
  • src/index.ts:186-199 (registration)
    Registration of the copy_object tool in the ListToolsRequestSchema response, defining name, description, and input schema.
    {
      name: 'copy_object',
      description: '复制对象',
      inputSchema: {
        type: 'object',
        properties: {
          sourceBucket: { type: 'string', description: '源存储桶名称' },
          sourceObject: { type: 'string', description: '源对象名称' },
          destBucket: { type: 'string', description: '目标存储桶名称' },
          destObject: { type: 'string', description: '目标对象名称' }
        },
        required: ['sourceBucket', 'sourceObject', 'destBucket', 'destObject']
      }
    },
  • Zod input validation schema used in the copy_object tool handler.
    const { sourceBucket, sourceObject, destBucket, destObject } = z.object({
      sourceBucket: z.string(),
      sourceObject: z.string(),
      destBucket: z.string(),
      destObject: z.string()
    }).parse(args);
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 of behavioral disclosure. '复制对象' implies a write operation (creating a copy), but it doesn't specify whether this requires specific permissions, overwrites existing destination objects, handles large files, or has rate limits. For a mutation tool with zero annotation coverage, this leaves critical behavioral traits undocumented.

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—just two characters in Chinese—and front-loaded with the core action. There is no wasted verbiage or unnecessary elaboration, making it efficient for quick scanning, though this brevity contributes to gaps in other dimensions.

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?

For a tool with 4 parameters, no annotations, and no output schema, the description is incomplete. It doesn't clarify the tool's role among siblings (e.g., vs. 'upload_file'), explain behavioral implications (like idempotency or error handling), or provide usage context. The high schema coverage helps, but the description alone is insufficient for safe and effective use.

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 input schema has 100% description coverage, with all four parameters clearly documented in Chinese (e.g., sourceBucket as '源存储桶名称'). The description adds no additional meaning beyond what the schema provides, such as explaining relationships between parameters (e.g., that source and destination can be the same bucket for renaming). Given the high schema coverage, a baseline score of 3 is appropriate.

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 '复制对象' (copy object) is a tautology that essentially restates the tool name 'copy_object' in Chinese. While it indicates the action (copy) and resource (object), it lacks specificity about what type of object is being copied (e.g., files in storage buckets) and doesn't distinguish this tool from potential siblings like 'upload_file' or 'download_file' that also involve object manipulation.

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 existing source/destination buckets), exclusions, or comparisons to sibling tools like 'upload_file' (for uploading new objects) or 'download_file' (for retrieving objects). Without such context, an agent must infer usage solely from the tool name and parameters.

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