Skip to main content
Glama
akave-ai

Akave MCP Server

by akave-ai

update_object

Overwrite existing objects in S3-compatible storage buckets by specifying bucket name, object key, and new content to update stored data.

Instructions

Update (overwrite) an object in a bucket

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesNew object content
bucketYesBucket name
keyYesObject key

Implementation Reference

  • The handler function for the 'update_object' MCP tool. It calls the S3Client's updateObject method with the provided bucket, key, and body, then returns a success response.
    async ({ bucket, key, body }) => {
      await this.s3Client.updateObject(bucket, key, body);
      return {
        content: [{ type: "text", text: JSON.stringify({ success: true }) }],
      };
    }
  • Input schema validation for the 'update_object' tool using Zod, defining bucket, key, and body parameters.
    {
      bucket: z.string().describe("Bucket name"),
      key: z.string().describe("Object key"),
      body: z.string().describe("New object content"),
    },
  • src/server.ts:180-194 (registration)
    Registration of the 'update_object' tool on the MCP server, including name, description, input schema, and handler.
    this.server.tool(
      "update_object",
      "Update (overwrite) an object in a bucket",
      {
        bucket: z.string().describe("Bucket name"),
        key: z.string().describe("Object key"),
        body: z.string().describe("New object content"),
      },
      async ({ bucket, key, body }) => {
        await this.s3Client.updateObject(bucket, key, body);
        return {
          content: [{ type: "text", text: JSON.stringify({ success: true }) }],
        };
      }
    );
  • Supporting helper method in S3Client class that implements object update by delegating to putObject (which overwrites existing objects).
    async updateObject(bucket: string, key: string, body: string) {
      // S3 putObject overwrites by default
      return this.putObject(bucket, key, body);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'overwrite', implying a destructive mutation, but doesn't specify permissions required, whether the operation is idempotent, error handling, or any rate limits. This leaves significant gaps for an agent to understand the tool's behavior.

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—a single, clear sentence that front-loads the essential information without any wasted words. It efficiently communicates the core action and target.

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 an update/overwrite operation, no annotations, and no output schema, the description is insufficient. It lacks details on behavioral traits, error conditions, and return values, making it incomplete for safe and effective tool invocation.

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, clearly documenting all three parameters (bucket, key, body). The description adds no additional semantic context beyond what's in the schema, such as format details or constraints, so it meets the baseline for high schema coverage.

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 ('Update (overwrite)') and resource ('an object in a bucket'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'put_object' or 'copy_object', which might have overlapping functionality, so it doesn't reach the highest score.

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 like 'put_object' or 'copy_object', nor does it mention prerequisites or exclusions. It's a bare statement of function with no contextual usage information.

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