Skip to main content
Glama
Sign In
AWS MCP Server

AWS MCP Server

by marcelobrake
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

aws_emr_list_clusters

List and filter Amazon EMR clusters in your AWS account by state, region, or profile to monitor and manage big data processing environments.

Instructions

List EMR clusters in the account/region.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "aws_emr_list_clusters"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNoAWS profile name from ~/.aws/config (e.g., 'default', 'production')
regionNoAWS region override (e.g., 'us-east-1', 'sa-east-1')
cluster_statesNoFilter by cluster states

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Zero annotations provided, yet the description carries full burden. Omits critical AWS API behaviors: whether results are paginated (they typically are), if the operation is read-only/safe, rate limiting considerations, or what fields are returned in the absence of an output schema.

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?

Single sentence is front-loaded and wastes no words. However, brevity arguably crosses into under-specification given the complexity of AWS EMR APIs and lack of supporting annotations or output schema.

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?

Inadequate for a 3-parameter AWS cloud API tool. Missing: output format details (since no output schema exists), pagination behavior, authentication requirements, and relationship to other EMR operations. The minimal description leaves agents guessing about critical operational aspects.

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?

Input schema has 100% description coverage, establishing a baseline of 3. The description mentions 'account/region' which loosely contextualizes the profile and region parameters, but adds no semantic clarity on cluster_states filtering or the fact that all three parameters are optional.

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?

States specific verb (List) and resource (EMR clusters) with scope (account/region). Deducting one point because it fails to distinguish from sibling tool aws_emr_describe_cluster, which retrieves detailed configuration of a specific cluster versus listing multiple clusters.

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 provided on when to use this listing tool versus the sibling aws_emr_describe_cluster for detailed views. No mention of typical use cases, prerequisites (AWS credentials), or when filtering by cluster_states is recommended.

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