Skip to main content
Glama
Sign In
AWS MCP Server

AWS MCP Server

by marcelobrake
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

aws_mwaa_get_environment

Retrieve detailed configuration and status information for Amazon Managed Workflows for Apache Airflow (MWAA) environments, including Airflow version, network settings, and web server URLs.

Instructions

Get detailed MWAA environment info: Airflow version, DAG S3 path, execution role, network config, logging, status, and web server URL.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It successfully discloses what data is returned via the attribute list, but omits operational details such as whether this requires specific MWAA read permissions, rate limiting, or that it is a non-destructive read operation.

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 sentence structured with the action first ('Get detailed MWAA environment info') followed by a colon-separated list of specific attributes. Every element earns its place with zero redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema exists, the description adequately compensates by listing specific return attributes. With 100% input schema coverage and no annotations, the description sufficiently covers the tool's purpose and output shape, though it could mention authentication/authorization requirements.

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?

Schema description coverage is 100%, establishing a baseline of 3. The description implies the 'name' parameter identifies the specific environment to retrieve, but adds no syntax details, example values, or format constraints beyond what the schema already provides.

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 uses specific verb 'Get' with resource 'MWAA environment' and enumerates specific attributes returned (Airflow version, DAG S3 path, etc.), clearly indicating detailed retrieval. However, it does not explicitly differentiate from sibling aws_mwaa_list_environments despite implying it through the detailed attribute list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage through the enumerated output attributes (use when you need these specific details), but lacks explicit guidance on when to use this versus the list_environments sibling or prerequisites like IAM permissions.

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