Skip to main content
Glama
akave-ai

Akave MCP Server

by akave-ai

delete_bucket

Remove a storage bucket from Akave's S3-compatible storage system to free up resources and manage your cloud storage infrastructure.

Instructions

Delete a bucket

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bucketYesBucket name

Implementation Reference

  • The main handler function for the delete_bucket tool, which delegates to s3Client.deleteBucket and returns a success response.
    async ({ bucket }) => {
      await this.s3Client.deleteBucket(bucket);
      return {
        content: [{ type: "text", text: JSON.stringify({ success: true }) }],
      };
    }
  • Zod input schema for the delete_bucket tool, defining the required 'bucket' parameter.
    {
      bucket: z.string().describe("Bucket name"),
    },
  • src/server.ts:267-279 (registration)
    Registration of the 'delete_bucket' MCP tool, including name, description, schema, and handler.
    this.server.tool(
      "delete_bucket",
      "Delete a bucket",
      {
        bucket: z.string().describe("Bucket name"),
      },
      async ({ bucket }) => {
        await this.s3Client.deleteBucket(bucket);
        return {
          content: [{ type: "text", text: JSON.stringify({ success: true }) }],
        };
      }
    );
  • S3Client helper method that executes the AWS DeleteBucketCommand.
    async deleteBucket(bucket: string) {
      const command = new DeleteBucketCommand({
        Bucket: bucket,
      });
      return await this.client.send(command);
    }
Behavior1/5

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

With no annotations provided, the description carries full burden but fails to disclose critical behavioral traits. It doesn't mention that deletion is irreversible, potential permissions required, effects on contained objects, or error conditions, leaving significant gaps for a destructive operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with 'Delete a bucket', which is front-loaded and wastes no words. However, it borders on under-specification given the tool's complexity, as more detail would be beneficial for clarity.

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 destructive tool with no annotations and no output schema, the description is incomplete. It lacks information on return values, error handling, and behavioral context, failing to compensate for the missing structured data and leaving the agent under-informed.

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 the parameter 'bucket' clearly documented as 'Bucket name'. The description adds no additional meaning beyond the schema, such as format constraints or examples, so it meets the baseline for high schema coverage without compensating value.

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

Purpose3/5

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

The description 'Delete a bucket' clearly states the action (delete) and resource (bucket), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'delete_object' or specify what constitutes a bucket versus an object, leaving room for confusion about scope.

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 such as 'delete_object' or prerequisites like bucket emptiness. The description lacks context about dependencies or exclusions, offering minimal help for tool selection.

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