Skip to main content
Glama
biswasbiplob

mwaa-mcp-server

by biswasbiplob
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

create-environment

Create a new Amazon MWAA environment by specifying DAGs S3 path, IAM role, VPC networking, and Airflow options. The operation runs asynchronously, with status CREATING until ready.

Instructions

Create a new MWAA environment.

    Creates an Amazon MWAA environment with the specified configuration. This operation
    is asynchronous — the environment status will be CREATING until ready.

    Requires the --allow-write flag.

    Args:
        ctx: The MCP context.
        environment_name: Name for the new environment.
        dag_s3_path: S3 path to the DAGs folder.
        execution_role_arn: IAM execution role ARN.
        source_bucket_arn: S3 bucket ARN for DAGs and plugins.
        network_configuration: VPC network configuration.
        airflow_version: Optional Airflow version.
        environment_class: Optional environment size class.
        max_workers: Optional maximum worker count.
        region: AWS region override.
        profile_name: AWS CLI profile name override.

    Returns:
        CallToolResult with the created environment ARN.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionNoAWS region. Defaults to AWS_REGION env var or us-east-1.
dag_s3_pathYesRelative path to the DAGs folder in the S3 bucket (e.g., "dags/").
max_workersNoMaximum number of workers for auto-scaling.
profile_nameNoAWS CLI profile name. Falls back to AWS_PROFILE env var.
airflow_versionNoApache Airflow version (e.g., "2.8.1"). Defaults to latest.
environment_nameYesName for the new MWAA environment (1-80 characters).
environment_classNoEnvironment class: "mw1.small", "mw1.medium", or "mw1.large".
source_bucket_arnYesARN of the S3 bucket containing DAGs and plugins.
execution_role_arnYesARN of the IAM execution role for the environment.
network_configurationYesNetwork configuration with SecurityGroupIds (list of VPC security group IDs) and SubnetIds (list of VPC subnet IDs, minimum 2 in different AZs).

Tool Definition Quality

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It transparently states that the operation is asynchronous, that the environment will show CREATING status until ready, that the --allow-write flag is needed, and that the return value is the created environment ARN. This is meaningful context beyond the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is concise and front-loaded, but the extensive Args/Returns block largely duplicates schema details. This adds length without adding value, though the structured layout keeps it readable. The description is not as tight as it should be.

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?

For a 10-parameter create operation with nested objects and no output schema, the description covers essential context: asynchronous behavior, required write flag, and return value. It could go further (e.g., mentioning how to poll status), but it's sufficiently complete for an agent to correctly invoke and interpret initial results.

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%, so the schema already documents each parameter. The description's Args list adds no new information and even introduces an extraneous 'ctx' parameter not present in the input schema. This repetition without additional semantic value aligns with the baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates a new MWAA environment with specific verbs ('Create', 'Creates') and a clear resource ('Amazon MWAA environment'). This distinctly differentiates it from siblings like get-environment, update-environment, and delete-environment.

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

Usage Guidelines4/5

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

The description provides clear context: it's for creating new environments, and it notes the async nature ('environment status will be CREATING until ready') and the prerequisite 'Requires the --allow-write flag'. However, it does not explicitly name alternatives or exclusion scenarios, so it stops short of a perfect score.

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/biswasbiplob/mwaa-mcp-server'

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