Skip to main content
Glama
MCP-Airflow-API

MCP-Airflow-API

by call518

dag_calendar

View a DAG's schedule and execution calendar for a date range to check planned run dates using its exact identifier and ISO 8601 start and end bounds.

Instructions

[Tool Role]: Shows DAG schedule and execution calendar for a date range.

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>",
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "dag_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
dag_idYesExact DAG identifier, as returned by list_dags; not its display name.
end_dateYesInclusive run start-time upper bound in ISO 8601 format.
start_dateYesInclusive run start-time lower bound in ISO 8601 format.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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 / end_date / description
      Added value: +"Inclusive run start-time upper bound in ISO 8601\nformat."
    • addedInput schema / properties / start_date / description
      Added value: +"Inclusive run start-time lower bound in ISO 8601\nformat."
  2. Addedv3.7.2
  3. Removedv3.6.5
  4. Changed4 schema fields changedv3.6.6
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / dag_id / title
      Removed value: -"Dag Id"
    • removedInput schema / properties / end_date / title
      Removed value: -"End Date"
    • removedInput schema / properties / start_date / title
      Removed value: -"Start Date"
  5. Changed4 schema fields changedv1.0.0
    • removedInput schema / properties / end_date / default
      Removed value: -null
    • removedInput schema / properties / limit
      Removed value: -{
      -  "default": 20,
      -  "title": "Limit",
      -  "type": "integer"
      -}
    • removedInput schema / properties / start_date / default
      Removed value: -null
    • changedInput schema / required
      Previous value: -[
      -  "dag_id"
      -]New value: +[
      +  "dag_id",
      +  "start_date",
      +  "end_date"
      +]
  6. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so the description carries the full burden. 'Shows' implies a read operation, but nothing states permission requirements, whether the calendar is computed vs stored, or behavior for missing DAGs. One sentence leaves most behavioral context undisclosed.

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?

Single front-loaded sentence with zero waste. It's efficient but arguably under-specified rather than maximally concise.

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?

Output schema exists and all required params are documented in schema, so minimal gaps. However, with no annotations and only one description sentence, an agent lacks guidance on when to use it and interpret calendar results.

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 each parameter has a clear description (dag_id exact identifier, ISO 8601 inclusive bounds). The description adds nothing beyond the schema, so baseline 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?

States a specific verb+resource: 'Shows DAG schedule and execution calendar.' Distinguishes it from siblings like list_dags or dag_graph, but doesn't name a sibling or clarify the boundary with dag_run_duration/dag_task_duration.

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 when-to-use guidance or alternatives mentioned. Only a hint that it's scoped to a date range; no indication when an agent should pick this over list_dags or dag_run_duration.

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