MCP-Airflow-API

get_dags_detailed_batch

Retrieve detailed information for multiple Airflow DAGs in a single batch, including latest run data, with optional filters for active/paused status and ID or name substrings.

Instructions

[Tool Role]: Retrieves detailed information for multiple DAGs in batch with latest run information.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_dags_detailed_batch"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`offset`	No
`fetch_all`	No
`is_active`	No
`is_paused`	No
`id_contains`	No
`name_contains`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0Jul 31, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits, but it only states that details and latest run information are returned. It does not explain pagination (limit/offset/fetch_all), filter behavior, or any side effects/authorization expectations. 'Retrieves' implies read-only, but the lack of detail about batching and pagination leaves important behavior unexplained.

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, front-loaded sentence with no unnecessary wording. It is concise and cleanly structured, though it sacrifices informative detail for 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?

Even though an output schema exists, the description is incomplete for a 7-parameter batch tool. It lacks pagination semantics, filter usage, and relationships to sibling tools, making it insufficient for an agent to invoke the tool correctly with all optional parameters.

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

Parameters1/5

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

The description mentions no parameters. Given 0% schema description coverage, the description carries the full burden of explaining limit, offset, fetch_all, is_active, is_paused, id_contains, and name_contains, but it fails to add any meaning beyond their names.

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 the tool's function with a specific verb ('Retrieves') and resource ('multiple DAGs in batch'), adding a key detail ('latest run information'). It distinguishes itself from siblings like get_dag (single DAG) and list_dags (summary listing) by emphasizing batch and detailed retrieval.

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 such as list_dags or get_dag. The phrase 'in batch' describes the operation rather than indicating when to choose it, and no exclusions or alternative recommendations are mentioned.

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

Deploy Server