Skip to main content
Glama
biswasbiplob

mwaa-mcp-server

by biswasbiplob
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get-dag-run

Retrieve the state, execution dates, and configuration of a specific DAG run in Amazon MWAA. Get the details you need to troubleshoot or audit a run.

Instructions

Get details of a specific DAG run.

    Returns detailed information about a DAG run including its state, execution date,
    start date, end date, and configuration.

    Args:
        ctx: The MCP context.
        environment_name: Name of the MWAA environment.
        dag_id: The DAG identifier.
        dag_run_id: The DAG run identifier.
        region: AWS region override.
        profile_name: AWS CLI profile name override.

    Returns:
        CallToolResult with DAG run details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dag_idYesThe DAG ID.
regionNoAWS region override.
dag_run_idYesThe DAG run ID.
profile_nameNoAWS CLI profile name override.
environment_nameNoName of the MWAA environment. If omitted and only one environment exists, it is used automatically.

Tool Definition Quality

A3.6/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 burden of disclosing behavior. It does not mention that this is a read-only operation, nor does it describe permission requirements, error conditions, or rate limits. It only lists return content, which is insufficient.

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 first sentence followed by Args and Returns sections. It is not excessively verbose, though the Args section largely duplicates schema information. It is front-loaded with the core purpose.

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

Completeness3/5

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

With no output schema, the description partially compensates by listing the returned fields (state, execution date, etc.), but it is vague about the exact response envelope ('CallToolResult'). It lacks details on error handling, prerequisites, or permissions, making it only minimally complete.

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 coverage is 100%, so baseline is 3. The description mostly repeats parameter names and descriptions from the schema, adding no meaningful extra context. The only extra is listing 'ctx' which is not in the schema. No behavioral nuance is added.

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 'Get details of a specific DAG run' with a specific verb and resource, and it distinguishes from sibling tools like list-dag-runs by focusing on a single run. It also lists the exact data returned (state, dates, configuration).

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 context is clear: this tool is for retrieving details of a specific DAG run, as opposed to listing runs. It does not explicitly mention alternatives or exclusions, but the 'specific' in the description implies when to use it.

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