MCP-Airflow-API

create_connection

Create a new Airflow connection by providing connection data. Use this tool to configure database or service credentials for workflows.

Instructions

[Tool Role]: Creates a new connection.

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": {
      "connection_data": "<connection_data>"
    },
    "name": "create_connection"
  }
}

Input Schema

Name	Required	Description	Default
`connection_data`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0Jul 31, 2026

TDQS

C2.4/5.0

Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It simply states 'Creates a new connection' without mentioning side effects, idempotency, required permissions, error conditions, or what happens if the connection already exists. This is a significant gap for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise, but it is under-specified rather than appropriately sized. It lacks critical details about the parameter and behavior, so the brevity is a result of omission, not effective compression.

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?

For a tool with one complex parameter (an open object) and no annotations or schema descriptions, the description is incomplete. It does not explain what a connection is, what fields connection_data accepts, or any behavioral consequences. The output schema exists but does not reduce the need for input guidance.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for the undocumented 'connection_data' parameter. It does not, leaving the agent without any explanation of what the parameter should contain, its format, or constraints. The parameter is an open object with additionalProperties true, making the absence of semantics particularly problematic.

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 a specific action ('Creates') and a specific resource ('a new connection'), which distinguishes it from sibling tools like list_connections, get_connection, update_connection, and delete_connection. The verb-resource pair is unambiguous and informative.

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. There is no mention of prerequisites, common use cases, or exclusions. Sibling tools like update_connection and delete_connection are not referenced, leaving the agent to infer usage from the name alone.

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

Deploy Server