Skip to main content
Glama

unpause_dag

Resume scheduling for paused Airflow DAGs to enable new workflow runs. This tool reactivates DAG execution within Apache Airflow clusters.

Instructions

[Tool Role]: Unpauses the specified Airflow DAG (allows scheduling new runs).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dag_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'unpause_dag' tool. It takes a dag_id parameter, validates it, sends a PATCH request to the Airflow API to set is_paused to False, and returns the updated DAG status.
    @mcp.tool()
    async def unpause_dag(dag_id: str) -> Dict[str, Any]:
        """[Tool Role]: Unpauses the specified Airflow DAG (allows scheduling new runs)."""
        if not dag_id:
            raise ValueError("dag_id must not be empty")
        resp = await airflow_request("PATCH", f"/dags/{dag_id}", json={"is_paused": False})
        resp.raise_for_status()
        dag_data = resp.json()
        return {
            "dag_id": dag_id,
            "is_paused": dag_data.get("is_paused")
        }
  • The @mcp.tool() decorator registers the unpause_dag function as an MCP tool within the register_common_tools function.
    @mcp.tool()
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. It mentions that unpausing 'allows scheduling new runs,' which adds some behavioral context, but it doesn't cover critical aspects like permissions required, side effects, error conditions, or what the output schema returns. This leaves significant gaps for a mutation tool.

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, efficient sentence that front-loads the core action and includes a helpful clarification. There's no wasted text, and the '[Tool Role]' prefix adds structure without verbosity.

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?

Given that this is a mutation tool with no annotations, one parameter, and an output schema exists (which reduces the need to describe return values), the description is adequate but incomplete. It covers the basic action but lacks details on behavioral traits and usage context, making it minimally viable.

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 0%, and the description doesn't mention the 'dag_id' parameter at all. However, with only one parameter and a clear tool name, the agent can infer the parameter's purpose. This meets the baseline for minimal viability but doesn't add value beyond what's obvious from context.

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 clearly states the verb ('unpauses') and resource ('specified Airflow DAG'), and it adds clarifying context ('allows scheduling new runs'). However, it doesn't explicitly differentiate from its sibling 'pause_dag' beyond the obvious opposite action, which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives like 'pause_dag' or other DAG management tools. It lacks context about prerequisites, such as whether the DAG must be paused first, or any exclusions for its use.

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/call518/MCP-Airflow-API'

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