Skip to main content
Glama
akave-ai

Akave MCP Server

by akave-ai

copy_object

Copy an object from one S3-compatible storage bucket to another bucket or location within Akave's storage system.

Instructions

Copy an object to another bucket/key

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
destinationBucketYesDestination bucket name
destinationKeyYesDestination object key
sourceBucketYesSource bucket name
sourceKeyYesSource object key

Implementation Reference

  • MCP tool handler function for 'copy_object' that calls s3Client.copyObject and returns success response
    async ({
      sourceBucket,
      sourceKey,
      destinationBucket,
      destinationKey,
    }) => {
      await this.s3Client.copyObject(
        sourceBucket,
        sourceKey,
        destinationBucket,
        destinationKey
      );
      return {
        content: [{ type: "text", text: JSON.stringify({ success: true }) }],
      };
    }
  • Input schema using Zod for copy_object tool parameters
    {
      sourceBucket: z.string().describe("Source bucket name"),
      sourceKey: z.string().describe("Source object key"),
      destinationBucket: z.string().describe("Destination bucket name"),
      destinationKey: z.string().describe("Destination object key"),
    },
  • src/server.ts:226-251 (registration)
    Registration of the 'copy_object' MCP tool including name, description, schema, and handler
    this.server.tool(
      "copy_object",
      "Copy an object to another bucket/key",
      {
        sourceBucket: z.string().describe("Source bucket name"),
        sourceKey: z.string().describe("Source object key"),
        destinationBucket: z.string().describe("Destination bucket name"),
        destinationKey: z.string().describe("Destination object key"),
      },
      async ({
        sourceBucket,
        sourceKey,
        destinationBucket,
        destinationKey,
      }) => {
        await this.s3Client.copyObject(
          sourceBucket,
          sourceKey,
          destinationBucket,
          destinationKey
        );
        return {
          content: [{ type: "text", text: JSON.stringify({ success: true }) }],
        };
      }
    );
  • S3Client helper method implementing the copy object logic using AWS SDK CopyObjectCommand
    async copyObject(
      sourceBucket: string,
      sourceKey: string,
      destinationBucket: string,
      destinationKey: string
    ) {
      const command = new CopyObjectCommand({
        Bucket: destinationBucket,
        Key: destinationKey,
        CopySource: `/${sourceBucket}/${sourceKey}`,
      });
      return await this.client.send(command);
    }
Behavior2/5

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

With no annotations, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits such as whether it overwrites existing destination objects, requires specific permissions, handles large files, has rate limits, or returns any output (e.g., success confirmation or error details).

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 with zero waste. It's front-loaded with the core action and resource, making it easy to scan and understand quickly without unnecessary details.

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 complexity of a copy operation with no annotations and no output schema, the description is incomplete. It lacks critical context like behavioral outcomes (e.g., overwrite behavior, error handling), return values, or usage constraints, leaving significant gaps for an AI agent to infer correctly.

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?

Schema description coverage is 100%, so the schema fully documents all 4 parameters. The description adds no additional meaning beyond implying source and destination contexts, which is already clear from parameter names. Baseline 3 is appropriate as the schema handles the heavy lifting.

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 ('Copy') and resource ('an object'), specifying the destination context ('to another bucket/key'). It distinguishes from siblings like 'get_object' (read) or 'put_object' (upload), but doesn't explicitly differentiate from similar tools like 'update_object' or mention if it overwrites existing 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 on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., permissions, existing source object), exclusions (e.g., cannot copy across regions), or compare to siblings like 'put_object' for uploads or 'get_object' + 'put_object' for manual copying.

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