Skip to main content
Glama
Sign In
AWS MCP Server

AWS MCP Server

by Havoc24k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

s3-list_buckets

Retrieve a complete list of all Amazon S3 buckets in your AWS account to manage storage resources and verify bucket configurations.

Instructions

List all S3 buckets in the AWS account

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "profile_name": "<profile_name>",
      "region": "<region>"
    },
    "name": "s3-list_buckets"
  }
}

Input Schema

NameRequiredDescriptionDefault
profile_nameYes
regionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

C2.8/5.0
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 it's a list operation but doesn't mention authentication requirements, rate limits, pagination behavior, or what happens if credentials are invalid. For a cloud API tool, this leaves critical operational context unspecified.

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, clear sentence with zero wasted words. It's appropriately sized for a simple list operation 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?

For a cloud API tool with 2 required parameters, 0% schema coverage, no annotations, and no output schema, the description is insufficient. It doesn't explain authentication, error conditions, return format, or parameter usage - leaving the agent with significant gaps in understanding how to use this tool effectively.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate but provides no parameter information. It doesn't explain what 'profile_name' or 'region' mean, their format, or why both are required. This leaves two required parameters completely undocumented beyond their schema titles.

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 in the AWS account'), making the purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 's3-list_objects_v2', which lists objects within a bucket rather than buckets themselves.

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. The description doesn't mention prerequisites like AWS credentials setup, nor does it differentiate from sibling tools like 's3-list_objects_v2' for listing bucket contents.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools