Skip to main content
Glama
MCP-Airflow-API

MCP-Airflow-API

by call518

update_connection

Modify an existing Airflow connection by providing its ID and updated JSON fields such as host, login, password, schema, port, or extra.

Instructions

[Tool Role]: Updates an existing 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>",
      "connection_data": "<connection_data>"
    },
    "name": "update_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
connection_idYesExact Airflow connection identifier.
connection_dataYesConnection JSON body containing fields to update, such as host, login, password, schema, port, or extra. Obtain credentials from a secret store; do not hardcode them.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.7.4
    • addedInput schema / properties / connection_data / description
      Added value: +"Connection JSON body containing fields to\nupdate, such as host, login, password, schema, port, or\nextra. Obtain credentials from a secret store; do not\nhardcode them."
    • addedInput schema / properties / connection_id / description
      Added value: +"Exact Airflow connection identifier."
  2. Addedv3.7.2
  3. Removedv3.6.5
  4. Changed3 schema fields changedv3.6.6
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / connection_data / title
      Removed value: -"Connection Data"
    • removedInput schema / properties / connection_id / title
      Removed value: -"Connection Id"
  5. Addedv1.0.0

TDQS

C2.3/5.0
Behavior2/5

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

With no annotations, the description bears the full behavioral burden and discloses almost nothing. It does not say whether the update is a partial merge or full replacement, whether it requires specific Airflow permissions, or whether changes are reversible. Only the bare fact that this mutates an existing resource is conveyed.

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?

The single sentence is efficient and front-loaded, but its brevity comes at the cost of under-specification rather than disciplined economy. It is short without being informative.

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 mutation tool with nested object parameters, no annotations, and no guidance, the description is incomplete: the critical question of partial-update vs full-replace semantics for connection_data is left unanswered. The existence of an output schema relieves the need to explain return values, but the update behavior itself is undocumented.

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%, so both parameters (connection_id, connection_data) are well documented in the schema, including the credential-handling caveat. The description adds no parameter meaning beyond the schema, so the baseline of 3 applies.

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 restates the tool name and title almost verbatim: "Updates an existing connection." It gives no detail on what aspects of a connection are updated nor how this differs from create_connection or delete_connection among the siblings. A specific verb+resource is present, but it is tautological rather than clarifying.

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?

No guidance on when to use this versus create_connection or delete_connection, and no prerequisites stated. The only implied condition is that the connection must already exist, which is carried entirely by the word "existing."

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