Skip to main content
Glama
call518

MCP-Airflow-API

by call518
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

delete_connection

Remove a specific connection from an Apache Airflow cluster to manage data pipeline configurations and maintain cluster organization.

Instructions

[Tool Role]: Deletes a connection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
connection_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/mcp_airflow_api/tools/common_tools.py:864-870 (handler)
    The core handler function for the 'delete_connection' tool. It performs a DELETE request to the Airflow connections endpoint using the shared airflow_request function. The @mcp.tool() decorator registers it directly within the common tools registration function.
    @mcp.tool()
async def delete_connection(connection_id: str) -> Dict[str, Any]:
    """[Tool Role]: Deletes a connection."""
    resp = await airflow_request("DELETE", f"/connections/{connection_id}")
    resp.raise_for_status()
    return {"message": f"Connection {connection_id} deleted successfully"}
  • src/mcp_airflow_api/tools/v1_tools.py:23-23 (registration)
    Registration call for v1 API tools. Invokes register_common_tools(mcp) which includes the delete_connection tool registration.
    common_tools.register_common_tools(mcp)
  • src/mcp_airflow_api/tools/v2_tools.py:24-24 (registration)
    Registration call for v2 API tools. Invokes register_common_tools(mcp) which includes the delete_connection tool registration.
    common_tools.register_common_tools(mcp)

Tool Definition Quality

C2.6/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Deletes' clearly indicates a destructive operation, the description doesn't specify whether deletion is permanent/reversible, what permissions are required, whether it affects dependent resources, or what the response looks like. For a destructive tool with zero annotation coverage, this is inadequate.

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 at just 4 words. While this brevity comes at the cost of completeness, every word earns its place by stating the core action and resource without any wasted text.

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 tool with 1 parameter (0% schema coverage), no annotations, and multiple sibling tools, the description is incomplete. It doesn't address critical context like deletion consequences, permissions, error conditions, or how this differs from related tools. The existence of an output schema helps but doesn't compensate for the missing behavioral and usage information.

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?

Schema description coverage is 0%, so the description must compensate for undocumented parameters. The description mentions 'a connection' but doesn't explain what 'connection_id' represents, how to obtain valid IDs, or provide any context about the parameter. With 1 parameter completely undocumented in both schema and description, this is insufficient.

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 the verb ('Deletes') and resource ('a connection'), which provides basic purpose clarity. However, it doesn't specify what a 'connection' is in this context or differentiate this tool from sibling tools like 'update_connection' or 'create_connection' beyond the obvious action difference.

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's no mention of prerequisites (e.g., needing to identify a connection first), consequences of deletion, or when deletion might be appropriate versus updating a connection instead.

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