Skip to main content
Glama
akave-ai

Akave MCP Server

by akave-ai

create_bucket

Create a new storage bucket in Akave's S3-compatible storage system to organize and manage your data objects.

Instructions

Create a new bucket

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bucketYesBucket name

Implementation Reference

  • Core handler function that creates an S3 bucket using CreateBucketCommand.
    async createBucket(bucket: string) {
      const command = new CreateBucketCommand({
        Bucket: bucket,
      });
      return await this.client.send(command);
    }
  • src/server.ts:253-265 (registration)
    MCP tool registration for 'create_bucket', including input schema and thin wrapper handler that delegates to S3Client.createBucket.
    this.server.tool(
      "create_bucket",
      "Create a new bucket",
      {
        bucket: z.string().describe("Bucket name"),
      },
      async ({ bucket }) => {
        await this.s3Client.createBucket(bucket);
        return {
          content: [{ type: "text", text: JSON.stringify({ success: true }) }],
        };
      }
    );
  • Zod input schema defining the 'bucket' parameter for the create_bucket tool.
    {
      bucket: z.string().describe("Bucket name"),
    },
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. 'Create a new bucket' implies a write operation but doesn't specify critical details: whether it requires specific permissions, if it's idempotent (e.g., fails if bucket exists), what happens on success (e.g., returns bucket details), or potential side effects. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 sentence 'Create a new bucket', which is front-loaded and wastes no words. Every word earns its place by directly stating the tool's purpose without unnecessary elaboration.

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 tool's complexity (a write operation with no annotations and no output schema), the description is incomplete. It doesn't explain what a 'bucket' is in this context, what the tool returns, error conditions, or behavioral traits. For a creation tool with 1 parameter and 100% schema coverage, the description should provide more context about the operation's outcome and usage.

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 the single parameter 'bucket' documented as 'Bucket name'. The description doesn't add any parameter semantics beyond this, such as naming constraints, format requirements, or examples. With high schema coverage, the baseline score of 3 is appropriate as the schema does 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 'Create a new bucket' clearly states the action (create) and resource (bucket) with a specific verb. It distinguishes this from sibling tools like 'delete_bucket' or 'list_buckets' by indicating creation rather than deletion or listing. However, it doesn't specify what type of bucket (e.g., storage bucket, data bucket) or provide additional context about the resource being created.

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. It doesn't mention prerequisites (e.g., permissions, existing resources), when not to use it (e.g., if a bucket already exists), or refer to sibling tools like 'list_buckets' for checking existing buckets first. The agent must infer usage from the tool name alone.

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