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

MCP-Airflow-API

by fastmcp-me
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

dag_calendar

View the schedule and execution calendar for an Airflow DAG over a specified date range.

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_idYes
end_dateYes
start_dateYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, and the description only states it 'Shows' something, implying a read-only operation. It does not disclose any other behavioral traits such as permissions, performance, or whether it includes manual runs.

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 concise sentence that is front-loaded and contains no filler. Every word contributes to the main point.

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?

Despite having an output schema and a simple parameter set, the description lacks usage guidelines and parameter semantics. An agent would need to infer too much, making the description insufficient for reliable selection and invocation.

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?

Schema description coverage is 0%, and the description does not elaborate on dag_id, start_date, or end_date beyond the tool name and the phrase 'date range'. It does not specify date formats or clarify what 'schedule and execution calendar' includes.

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 uses the specific verb 'Shows' and identifies the resource as 'DAG schedule and execution calendar', scoped by a date range. It distinguishes from sibling tools like list_dags or get_dag, though 'execution calendar' could be slightly ambiguous.

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 provides no guidance on when to use this tool versus alternatives such as list_dags or dag_graph. It does not mention prerequisites, exclusions, or specific use cases.

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