MCP-Airflow-API

pause_dag

Pause a specified Airflow DAG to prevent new runs. Provide the DAG ID to stop scheduling immediately.

Instructions

[Tool Role]: Pauses the specified Airflow DAG (prevents scheduling new runs).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dag_id": "<dag_id>"
    },
    "name": "pause_dag"
  }
}

Input Schema

Name	Required	Description	Default
`dag_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0Jul 31, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the key behavioral effect (prevents scheduling new runs), which implies existing runs are not stopped, but it omits other details such as reversibility, idempotency, or permission requirements.

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 sentence that is front-loaded with the verb and resource, contains zero waste, and efficiently states the core effect.

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?

Given the tool's simplicity (one parameter, no nested objects, and an existing output schema), the description adequately covers the action and effect. Minor missing context about usage guidelines prevents a higher score, but the core purpose is well captured.

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 only parameter 'dag_id' has 0% schema description coverage, and the description only vaguely references 'the specified Airflow DAG' without explicitly defining the parameter, its format, or how to obtain it. This does not compensate for the lack of schema detail.

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 uses a specific verb ('Pauses') and resource ('Airflow DAG'), and the parenthetical 'prevents scheduling new runs' clarifies the action's effect. It clearly distinguishes from the sibling tool 'unpause_dag' by direction.

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

Usage Guidelines3/5

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

The description implies usage context by noting it prevents scheduling, but it does not explicitly state when to use this tool versus alternatives like 'unpause_dag' or 'trigger_dag', nor does it mention prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server