Skip to main content
Glama
Sign In
MCP-Airflow-API

MCP-Airflow-API

by call518
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

dag_task_duration

Measure and compare task durations in a DAG run to pinpoint slow tasks and improve Airflow workflow efficiency.

Instructions

[Tool Role]: Analyzes task durations within a DAG run.

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": "dag_task_duration"
  }
}

Input Schema

NameRequiredDescriptionDefault
dag_idYesExact DAG identifier, as returned by list_dags; not its display name.
dag_run_idNoDAG run identifier; omitted or empty selects the latest run.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.7.4
    • addedInput schema / properties / dag_id / description
      Added value: +"Exact DAG identifier, as returned by list_dags; not its\ndisplay name."
    • addedInput schema / properties / dag_run_id / description
      Added value: +"DAG run identifier; omitted or empty selects the\nlatest run."
  2. Addedv3.7.2
  3. Removedv3.6.5
  4. Changed3 schema fields changedv3.6.6
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / dag_id / title
      Removed value: -"Dag Id"
    • removedInput schema / properties / dag_run_id / title
      Removed value: -"Dag Run Id"
  5. Changed2 schema fields changedv1.0.0
    • addedInput schema / properties / dag_run_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Dag Run Id"
+}
    • removedInput schema / properties / run_id
      Removed value: -{
-  "default": null,
-  "title": "Run Id",
-  "type": "string"
-}
  6. First observed

TDQS

C2.5/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 full behavioral burden and does not meet it: it does not state read-only vs mutating nature, permission requirements, cost, or result size. Nothing is contradicted, but almost nothing beyond the name is disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short, front-loaded sentence with no waste, but it errs toward under-specification rather than conciseness. The '[Tool Role]' label adds no information an agent can act on.

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?

For a two-parameter analysis tool with no annotations, one sentence is insufficient: what 'analysis' means (per-task durations? totals? comparisons?) is left undefined, and no usage context is given. The existing output schema helps with return-value shape, but the description still leaves the agent guessing about the tool's actual behavior.

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% and both parameters are well documented in the schema, including the 'omitted selects latest run' default behavior, so the schema does the heavy lifting. The description adds no parameter meaning of its own, which is the baseline expectation here.

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?

States a resource (task durations within a DAG run) and implies a read/compute operation, which does separate it from the sibling dag_run_duration (whole-run duration). But the verb 'analyzes' is vague — it never says whether this aggregates, compares, or ranks task durations — so the agent cannot tell precisely what the tool produces.

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?

There is no when-to-use guidance and no mention of alternatives, despite obvious siblings such as dag_run_duration, list_tasks, and list_task_instances_all that overlap in scope. The agent must infer from the name alone which of these to pick.

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

Deploy Server

Other Tools