Skip to main content
Glama
akave-ai

Akave MCP Server

by akave-ai

get_bucket_location

Retrieve the AWS region or geographic location where an S3-compatible storage bucket is hosted to ensure proper API endpoint configuration and data residency compliance.

Instructions

Get the region/location of a bucket

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bucketYesBucket name

Implementation Reference

  • The MCP tool handler function for 'get_bucket_location' that invokes the S3 client's getBucketLocation method and formats the response as MCP content.
    async ({ bucket }) => {
      const location = await this.s3Client.getBucketLocation(bucket);
      return {
        content: [{ type: "text", text: JSON.stringify(location) }],
      };
    }
  • Zod input schema for the 'get_bucket_location' tool, validating the 'bucket' parameter.
    {
      bucket: z.string().describe("Bucket name"),
    },
  • src/server.ts:281-293 (registration)
    Registration of the 'get_bucket_location' MCP tool, including name, description, input schema, and inline handler function.
    this.server.tool(
      "get_bucket_location",
      "Get the region/location of a bucket",
      {
        bucket: z.string().describe("Bucket name"),
      },
      async ({ bucket }) => {
        const location = await this.s3Client.getBucketLocation(bucket);
        return {
          content: [{ type: "text", text: JSON.stringify(location) }],
        };
      }
    );
  • Helper method in S3Client class that sends GetBucketLocationCommand to retrieve the bucket's location/region.
    async getBucketLocation(bucket: string) {
      const command = new GetBucketLocationCommand({
        Bucket: bucket,
      });
      return await this.client.send(command);
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states a read operation ('Get'), implying it's likely safe and non-destructive, but doesn't specify permissions needed, rate limits, error conditions, or what the return format looks like (e.g., string, object). This leaves significant gaps for a tool with no annotation coverage.

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 that directly states the tool's purpose with zero wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., permissions, errors), return values, and usage context. For a simple tool, this might be minimally adequate, but it doesn't provide enough information for confident agent use without additional context.

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 single parameter 'bucket' clearly documented in the schema. The description doesn't add any meaning beyond this (e.g., format constraints, examples), so it meets the baseline score of 3 where 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 clearly states the action ('Get') and resource ('region/location of a bucket'), making the purpose immediately understandable. However, it doesn't distinguish this tool from its siblings (like 'fetch_headers' or 'get_object'), which might also retrieve bucket-related information, 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. It doesn't mention prerequisites (e.g., bucket existence), exclusions, or comparisons to siblings like 'list_buckets' or 'fetch_headers', leaving usage context unclear.

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