Skip to main content
Glama
call518

MCP-Airflow-API

by call518
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

list_connections

Retrieve all configured connections from Apache Airflow to manage data pipelines and external integrations.

Instructions

[Tool Role]: Lists all connections in Airflow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/mcp_airflow_api/tools/common_tools.py:834-842 (handler)
    Implementation of the list_connections MCP tool handler. Fetches paginated list of Airflow connections using the generic airflow_request function.
    @mcp.tool()
async def list_connections(limit: int = 20, offset: int = 0) -> Dict[str, Any]:
    """[Tool Role]: Lists all connections in Airflow."""
    params = {'limit': limit, 'offset': offset}
    query_string = "&".join([f"{k}={v}" for k, v in params.items()])
    resp = await airflow_request("GET", f"/connections?{query_string}")
    resp.raise_for_status()
    return resp.json()
  • src/mcp_airflow_api/tools/v1_tools.py:23-23 (registration)
    Registration call for all common tools (including list_connections) in the v1 tools module.
    common_tools.register_common_tools(mcp)
  • src/mcp_airflow_api/tools/v2_tools.py:24-24 (registration)
    Registration call for all common tools (including list_connections) in the v2 tools module.
    common_tools.register_common_tools(mcp)

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states what the tool does ('Lists all connections'), with no information about permissions required, rate limits, pagination behavior (implied by limit/offset parameters but not explained), or what the output contains. For a list tool with no annotation coverage, this is a significant gap in transparency.

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, efficient sentence with zero waste. It is appropriately sized for a simple list tool and front-loaded with the core purpose. Every word earns its place, making it highly concise and well-structured.

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?

Given the tool's low complexity (list operation), no annotations, and an output schema exists (which should cover return values), the description is minimally complete. However, it lacks parameter explanations and behavioral context, making it adequate but with clear gaps. The output schema reduces the need to describe returns, but the description does not fully compensate for missing parameter and usage details.

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?

The input schema has 2 parameters (limit, offset) with 0% schema description coverage, meaning the schema provides no semantic information. The description does not mention parameters at all, failing to compensate for the coverage gap. It does not explain what 'limit' and 'offset' do, their default values, or how they affect the listing.

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 clearly states the tool's purpose as 'Lists all connections in Airflow', which is a specific verb ('Lists') and resource ('connections in Airflow'). It distinguishes from siblings like 'get_connection' (singular) and 'create_connection'/'delete_connection'/'update_connection' (mutations), but does not explicitly differentiate from other list tools like 'list_dags' or 'list_variables' beyond the resource type.

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. It does not mention when to use it over 'get_connection' for a single connection, or how it relates to other list tools. There are no explicit when/when-not statements or named alternatives, leaving usage context implied at best.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/call518/MCP-Airflow-API'

If you have feedback or need assistance with the MCP directory API, please join our Discord server