Skip to main content
Glama
MCP-Airflow-API

MCP-Airflow-API

by call518

get_dags_detailed_batch

Retrieves detailed information for multiple Airflow DAGs in one batch, including latest run details, with filters for active/paused status, IDs, names, and pagination.

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

NameRequiredDescriptionDefault
limitNoMaximum number of records to request per page. Default: 100.
offsetNoNumber of records to skip for pagination. Default: 0.
fetch_allNoFetch every DAG page; ignores limit and offset when True. Default: False.
is_activeNoOptional active-status filter; None includes both statuses. Default: None.
is_pausedNoOptional paused-status filter; None includes both statuses. Default: None.
id_containsNoOptional substring to match against DAG identifiers. Default: None.
name_containsNoOptional substring to match against DAG display names. Default: None.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv3.7.4
    • addedInput schema / properties / fetch_all / description
      Added value: +"Fetch every DAG page; ignores limit and offset when\nTrue. Default: False."
    • addedInput schema / properties / id_contains / description
      Added value: +"Optional substring to match against DAG\nidentifiers. Default: None."
    • addedInput schema / properties / is_active / description
      Added value: +"Optional active-status filter; None includes both\nstatuses. Default: None."
    • addedInput schema / properties / is_paused / description
      Added value: +"Optional paused-status filter; None includes both\nstatuses. Default: None."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of records to request per page. Default:\n100."
    • addedInput schema / properties / name_contains / description
      Added value: +"Optional substring to match against DAG display\nnames. Default: None."
    • addedInput schema / properties / offset / description
      Added value: +"Number of records to skip for pagination. Default: 0."
  2. Addedv3.7.2
  3. Removedv3.6.5
  4. Changed8 schema fields changedv3.6.6
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / fetch_all / title
      Removed value: -"Fetch All"
    • removedInput schema / properties / id_contains / title
      Removed value: -"Id Contains"
    • removedInput schema / properties / is_active / title
      Removed value: -"Is Active"
    • removedInput schema / properties / is_paused / title
      Removed value: -"Is Paused"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / name_contains / title
      Removed value: -"Name Contains"
    • removedInput schema / properties / offset / title
      Removed value: -"Offset"
  5. First observed

TDQS

B3.2/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 behavioral burden. 'Retrieves' implies a read-only operation, and 'batch with latest run information' conveys useful scope, but the description does not explicitly state side-effect safety, pagination behavior, rate limits, or how the detailed output differs from simpler list tools. The output schema helps with return format, but usage behavior remains thin.

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 wasted text. The '[Tool Role]:' placeholder adds minor noise, and 'detailed information' is somewhat vague, but the structure is efficient.

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?

The tool has seven optional parameters, full schema descriptions, and an output schema, so the description need not repeat parameter or return details. However, with no annotations and no sibling routing guidance, the one-sentence description is only minimally complete for a batch retrieval tool.

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 100%, so all seven parameters are documented in the schema. The description does not add meaning beyond the schema for pagination, filters, or fetch_all behavior, so the baseline of 3 is appropriate.

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 states a specific verb and resource: retrieves detailed information for multiple DAGs in batch. It adds the scope of including latest run information, making the purpose clear. It does not explicitly distinguish this from siblings such as list_dags or get_dag, so it falls short of a 5.

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 gives no guidance on when to use this tool versus alternatives like list_dags, get_dag, running_dags, or failed_dags. There are no exclusions, prerequisites, or contextual recommendations for selecting this batch-detailed variant.

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