Skip to main content
Glama
biswasbiplob

mwaa-mcp-server

by biswasbiplob
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

update-environment

Update an existing MWAA environment's configuration: Airflow version, environment class, worker count, DAG S3 path, or IAM roles. Only specified parameters are changed, asynchronously.

Instructions

Update an existing MWAA environment.

    Updates the specified MWAA environment configuration. Only provided parameters
    will be updated. This operation is asynchronous.

    Requires the --allow-write flag.

    Args:
        ctx: The MCP context.
        environment_name: Name of the environment to update.
        airflow_version: Optional new Airflow version.
        environment_class: Optional new environment class.
        max_workers: Optional new max workers.
        dag_s3_path: Optional new DAG S3 path.
        execution_role_arn: Optional new execution role ARN.
        source_bucket_arn: Optional new source bucket ARN.
        region: AWS region override.
        profile_name: AWS CLI profile name override.

    Returns:
        CallToolResult with the update confirmation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionNoAWS region. Defaults to AWS_REGION env var or us-east-1.
dag_s3_pathNoNew relative path to the DAGs folder in S3.
max_workersNoNew maximum number of workers.
profile_nameNoAWS CLI profile name. Falls back to AWS_PROFILE env var.
airflow_versionNoNew Apache Airflow version.
environment_nameYesName of the MWAA environment to update.
environment_classNoNew environment class: "mw1.small", "mw1.medium", or "mw1.large".
source_bucket_arnNoNew S3 bucket ARN.
execution_role_arnNoNew IAM execution role ARN.

Tool Definition Quality

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of disclosing behavior. It states the operation is asynchronous, requires the --allow-write flag, and only provided parameters are updated. This gives the agent essential safety and execution context, though it stops short of describing side effects like potential downtime or environment restart.

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?

The description is well-structured with a clear opening sentence, auth requirement, and a formatted Args list. The Args list is somewhat redundant with the schema, but the overall description is scannable and contains no filler. It earns its length by adding behavioral details.

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 9-parameter async mutation with no output schema, the description covers the main purpose, partial update behavior, async nature, auth requirement, and the return type. It could mention prerequisites like the environment existing or potential errors, but it is largely complete for an update tool.

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

Parameters4/5

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

All 9 parameters have full schema descriptions, so the baseline is 3. The description adds the crucial semantic that omitted parameters are left unchanged ('Only provided parameters will be updated'), which is essential for correct partial updates. This goes beyond what the schema states.

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 updates an existing MWAA environment. It also notes that only provided parameters are updated, which cleanly distinguishes it from create-environment, delete-environment, and get-environment. The verb 'update' plus the resource 'MWAA environment' is specific and unambiguous.

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 phrase 'Update an existing MWAA environment' and 'Only provided parameters will be updated' give clear context for when to use this tool: to modify an existing environment, not to create or delete one. However, it does not explicitly name alternatives like create-environment or get-environment, so it lacks explicit exclusions.

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