Skip to main content
Glama
MCP-Airflow-API

MCP-Airflow-API

by call518

delete_connection

Deletes an Apache Airflow connection by exact connection ID to remove obsolete or incorrect configurations from the cluster.

Instructions

[Tool Role]: Deletes a 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_id": "<connection_id>"
    },
    "name": "delete_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
connection_idYesExact Airflow connection identifier.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.7.4
    • addedInput schema / properties / connection_id / description
      Added value: +"Exact Airflow connection identifier."
  2. Addedv3.7.2
  3. Removedv3.6.5
  4. Changed2 schema fields changedv3.6.6
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / connection_id / title
      Removed value: -"Connection Id"
  5. Addedv1.0.0

TDQS

C2.5/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, but it only says "Deletes". It does not state whether deletion is permanent or reversible, whether it cascades to dependent DAGs/tasks, or what permissions/authorization are required for a destructive Airflow connection operation.

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

Conciseness3/5

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

It is a single short, front-loaded sentence with no filler, but its terseness reflects under-specification rather than efficient conciseness. The one sentence barely earns its place because it adds nothing beyond the tool name.

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 destructive mutation tool with no annotations, the description should at minimum note irreversibility, permissions, and effect on referenced objects; all are absent. An output schema exists, so return-value explanation is not required, but the behavioral gaps remain significant.

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 description coverage is 100%, with the single required parameter connection_id documented as an "Exact Airflow connection identifier". The description adds no further parameter meaning, but the baseline is 3 when the schema does the heavy lifting.

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

Purpose3/5

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

The description states a clear verb and resource ("Deletes a connection"), so an agent can tell what it does at a glance. However, it essentially restates the tool name and offers no differentiation from closely related siblings such as create_connection or update_connection.

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?

There is no guidance on when to use this tool versus the alternatives; the sibling set includes create_connection and update_connection, yet the description does not mention them or any preconditions. The agent must infer that this is the destructive counterpart to those tools.

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