Skip to main content
Glama
call518

MCP-Airflow-API

by call518
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

create_connection

Add a new connection to Apache Airflow clusters for data pipeline integration, enabling task monitoring and DAG inspection through the MCP server.

Instructions

[Tool Role]: Creates a new connection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
connection_dataYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/mcp_airflow_api/tools/common_tools.py:851-856 (handler)
    The core implementation of the 'create_connection' MCP tool handler. It performs a POST request to Airflow's /connections endpoint using the provided connection_data dictionary.
    async def create_connection(connection_data: Dict[str, Any]) -> Dict[str, Any]:
    """[Tool Role]: Creates a new connection."""
    resp = await airflow_request("POST", "/connections", json=connection_data)
    resp.raise_for_status()
    return resp.json()
  • src/mcp_airflow_api/tools/v1_tools.py:23-23 (registration)
    Registration invocation for Airflow v1 tools, which includes the create_connection tool via common_tools.register_common_tools(mcp).
    common_tools.register_common_tools(mcp)
  • src/mcp_airflow_api/tools/v2_tools.py:24-24 (registration)
    Registration invocation for Airflow v2 tools, which includes the create_connection tool via common_tools.register_common_tools(mcp).
    common_tools.register_common_tools(mcp)

Tool Definition Quality

C2.1/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. It states 'Creates a new connection', implying a write/mutation operation, but fails to describe permissions required, side effects, error conditions, or response format. For a mutation tool with zero 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 extremely concise with a single sentence '[Tool Role]: Creates a new connection.' It is front-loaded and wastes no words, though this brevity contributes to its inadequacy in other dimensions. Every part of the description serves a purpose, earning a high score for conciseness.

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?

Given the tool's complexity (a mutation with one nested object parameter, no annotations, but an output schema exists), the description is incomplete. It does not explain what a 'connection' is, how to structure the input, or what to expect in return. While the output schema may cover return values, the description fails to provide essential context for effective tool use.

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 schema description coverage is 0%, with one parameter 'connection_data' documented only as an object with no properties described. The description adds no information about what 'connection_data' should contain, its structure, or examples. It does not compensate for the lack of schema details, leaving the parameter's semantics unclear.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Creates a new connection' restates the tool name 'create_connection' without adding specificity about what a 'connection' is or what resource it creates. While it includes a verb ('Creates') and resource ('connection'), it lacks differentiation from sibling tools like 'update_connection' or 'get_connection', making it a tautology that provides minimal additional insight.

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

Usage Guidelines1/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 prerequisites, context, or exclusions, nor does it reference sibling tools such as 'update_connection' or 'list_connections' for comparison. This leaves the agent without direction on appropriate usage scenarios.

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