Skip to main content
Glama
Sign In
AWS MCP Server

AWS MCP Server

by marcelobrake
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

aws_emr_describe_cluster

Retrieve detailed configuration and status information for an Amazon EMR cluster by providing its cluster ID.

Instructions

Get detailed information about an EMR cluster.

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": {
      "cluster_id": "<cluster_id>"
    },
    "name": "aws_emr_describe_cluster"
  }
}

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_idYesCluster ID (e.g., j-XXXXX)

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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Get' implies read-only access, the description does not confirm safety, mention required AWS permissions, explain what 'detailed information' includes (status, configuration, instances), or disclose latency/cost implications of the AWS API call.

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 with 7 words. Every word earns its place with no redundancy. However, given the absence of annotations and output schema, the extreme brevity shifts the burden of discovery entirely to the schema and tool name.

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?

Lacks output schema and fails to hint at return value structure (cluster status, applications, hardware). Does not exploit the high schema coverage to provide usage examples or explain the relationship between the 'profile'/'region' parameters and the target cluster. Incomplete for an AWS API tool with behavioral complexity.

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 for all 3 parameters (profile, region, cluster_id). Since schema coverage is high, baseline score is 3. The description adds no semantic context beyond what the schema already provides, but does not need to compensate for missing schema documentation.

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?

Provides specific verb ('Get') and resource ('EMR cluster'), making the basic function clear. However, it fails to explicitly distinguish from sibling 'aws_emr_list_clusters' (summary list vs. single detailed view), which is crucial for agent selection among AWS EMR tools.

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?

Contains no guidance on when to use this tool versus 'aws_emr_list_clusters' or 'aws_emr_list_steps', nor does it mention the prerequisite of obtaining a cluster_id from a list operation first. Zero guidance on alternatives or prerequisites.

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