Skip to main content
Glama
Sign In
airflow-mcp-server

airflow-mcp-server

by us-all
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search-tools

Search available Airflow MCP tools using natural language queries. Filter by category and limit to find the right tool.

Instructions

Discover available Airflow MCP tools by natural language query.

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": {
      "query": "<query>"
    },
    "name": "search-tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesNatural language query. Discover available Airflow MCP tools — call this first to find the right tool.
categoryNoRestrict search to a specific category
limitNoMax results (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.4
  2. Removedv1.0.2
  3. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses the tool's purpose as a discovery tool but does not mention read-only behavior, rate limits, or side effects. For a search tool, this is adequate but leaves some ambiguity.

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, front-loaded sentence with no wasted words. It conveys the essential purpose and usage guidance efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity of the tool (3 parameters, all documented, no output schema), the description covers the core purpose and entry-point guidance. Missing details about output format, but the agent can infer a list of tools.

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%, so the baseline is 3. The description does not add new semantic info beyond the schema; it repeats 'call this first' which is already in the query parameter description.

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 verb 'Discover' and the resource 'available Airflow MCP tools' via natural language query. This distinguishes it from sibling tools which are specific Airflow operations (e.g., clear task, trigger DAG).

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

Usage Guidelines4/5

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

The description explicitly advises 'call this first to find the right tool,' providing clear when-to-use guidance. It lacks explicit exclusions or alternatives but strongly implies this is the entry point.

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