Skip to main content
Glama

s3_bucket_list

List all S3 buckets in your AWS account to manage storage, monitor resources, and organize cloud data.

Instructions

List all S3 buckets

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Executes the s3_bucket_list tool by calling list_buckets() on the boto3 S3 client to list all S3 buckets.
    elif name == "s3_bucket_list":
        response = s3_client.list_buckets()
  • Defines the Tool object for s3_bucket_list, including name, description, and input schema (no required properties).
    Tool(
        name="s3_bucket_list",
        description="List all S3 buckets",
        inputSchema={
            "type": "object",
            "properties": {}
        }
    ),
  • Registers the list_tools handler which returns all AWS tools, including s3_bucket_list via get_aws_tools().
    @server.list_tools()
    async def list_tools() -> list[Tool]:
        """List available AWS tools"""
        logger.debug("Handling list_tools request")
        return get_aws_tools()
  • Dispatches s3_bucket_list calls to the handle_s3_operations function in the main call_tool handler.
    try:
        if name.startswith("s3_"):
            return await handle_s3_operations(aws, name, arguments)
        elif name.startswith("dynamodb_"):
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'List all S3 buckets' implies a read-only operation but doesn't disclose behavioral traits like whether it requires specific permissions, returns paginated results, includes metadata, or has rate limits. For a tool with zero annotation coverage, this is inadequate.

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 wasted words. It's appropriately sized for a simple tool and front-loads the core functionality immediately.

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 simplicity (0 parameters, no output schema) but lack of annotations, the description is incomplete. It doesn't address what the list returns (e.g., bucket names, ARNs, creation dates), potential errors, or behavioral context needed for an AI agent to use it effectively without annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the absence of inputs. The description doesn't need to add parameter details, and it correctly implies no filtering or options are available, earning a baseline score of 4 for this dimension.

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 verb ('List') and resource ('all S3 buckets'), making the purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 's3_object_list' which lists objects within a bucket rather than buckets themselves, so it misses full sibling differentiation.

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 's3_object_list' or 'dynamodb_table_list'. It doesn't mention prerequisites, authentication needs, or any context for selection among the many sibling tools provided.

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/rishikavikondala/mcp-server-aws'

If you have feedback or need assistance with the MCP directory API, please join our Discord server