Skip to main content
Glama
Sign In
Airflow MCP

Airflow MCP

by zamax14
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_dags

Retrieve Airflow DAGs with optional filters for tags, active state, limit, and offset.

Instructions

List Airflow DAGs, optionally filtered by tag or active state.

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

Input Schema

NameRequiredDescriptionDefault
tagsNo
limitNo
offsetNo
only_activeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations exist, so description carries full burden. It only states the basic action without disclosing read-only nature, performance implications, pagination behavior, or potential rate limits.

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?

Extremely concise and front-loaded with the core action and optional filters. No wasted words.

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, so return values are covered. However, missing context on pagination (limit/offset), sorting, and full filtering capabilities leaves gaps for effective use.

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 0%, so description must compensate. It mentions 'tag or active state' which maps to tags and only_active, but does not explain limit, offset, or parameter formats. Adds some value but insufficient.

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 it lists DAGs with optional filtering by tag or active state. It distinguishes from siblings like get_dag (single DAG) and list_dag_runs (runs).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this vs alternatives. While implied, it does not mention that get_dag is for a specific DAG or that list_dag_runs is for runs.

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