Skip to main content
Glama
yangkyeongmo

MCP Server for Apache Airflow

by yangkyeongmo

reparse_dag_file

Reparse a DAG file in Apache Airflow to update its configuration and trigger execution after changes.

Instructions

Request re-parsing of a DAG file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_tokenYes

Implementation Reference

  • The MCP tool handler function that invokes the Airflow DAG API to reparse a DAG file using the provided file_token and returns the response.
    async def reparse_dag_file(
        file_token: str,
    ) -> List[Union[types.TextContent, types.ImageContent, types.EmbeddedResource]]:
        response = dag_api.reparse_dag_file(file_token=file_token)
        return [types.TextContent(type="text", text=str(response.to_dict()))]
  • The registration of the reparse_dag_file tool in the list of all functions returned for MCP tool registration.
    def get_all_functions() -> list[tuple[Callable, str, str, bool]]:
        """Return list of (function, name, description, is_read_only) tuples for registration."""
        return [
            (get_dags, "fetch_dags", "Fetch all DAGs", True),
            (get_dag, "get_dag", "Get a DAG by ID", True),
            (get_dag_details, "get_dag_details", "Get a simplified representation of DAG", True),
            (get_dag_source, "get_dag_source", "Get a source code", True),
            (pause_dag, "pause_dag", "Pause a DAG by ID", False),
            (unpause_dag, "unpause_dag", "Unpause a DAG by ID", False),
            (get_dag_tasks, "get_dag_tasks", "Get tasks for DAG", True),
            (get_task, "get_task", "Get a task by ID", True),
            (get_tasks, "get_tasks", "Get tasks for DAG", True),
            (patch_dag, "patch_dag", "Update a DAG", False),
            (patch_dags, "patch_dags", "Update multiple DAGs", False),
            (delete_dag, "delete_dag", "Delete a DAG", False),
            (clear_task_instances, "clear_task_instances", "Clear a set of task instances", False),
            (set_task_instances_state, "set_task_instances_state", "Set a state of task instances", False),
            (reparse_dag_file, "reparse_dag_file", "Request re-parsing of a DAG file", False),
        ]
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. It mentions 'Request re-parsing', which implies a mutation or action, but doesn't clarify if this is idempotent, requires specific permissions, has side effects (e.g., clearing runs), or what happens on success/failure. For a tool with no annotations, this leaves significant gaps in understanding its behavior and safety.

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 a single, efficient sentence with no wasted words, making it easy to parse. However, it's front-loaded but under-specified—while concise, it could benefit from slightly more detail to improve clarity without losing brevity.

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?

Given the complexity (a mutation tool with no annotations, 1 undocumented parameter, and no output schema), the description is incomplete. It doesn't explain what re-parsing does, the expected outcome, error conditions, or how it interacts with the system (e.g., Airflow DAGs). For a tool that likely triggers server-side processing, more context is needed to use it effectively.

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

Parameters2/5

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

The input schema has 1 parameter with 0% description coverage, so the schema provides no semantic information. The description adds no details about the 'file_token' parameter (e.g., what it represents, how to obtain it, format constraints). This fails to compensate for the low schema coverage, leaving the parameter's meaning and usage unclear.

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

Purpose3/5

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

The description states the action ('Request re-parsing') and resource ('a DAG file'), which provides a basic understanding of purpose. However, it's vague about what 're-parsing' entails (e.g., does it trigger validation, reloading, or error detection?) and doesn't distinguish from siblings like 'patch_dag' or 'get_dag_source' that might involve DAG file operations. It avoids tautology by not merely restating the name.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't specify if this should be used after editing a DAG file, to fix parsing errors, or as an alternative to 'patch_dag'. The context is implied (e.g., after file changes), but no explicit when/when-not or sibling comparisons are made, leaving the agent to guess based on the name alone.

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/yangkyeongmo/mcp-server-apache-airflow'

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