Skip to main content
Glama
nikhil-ganage

MCP Server Airflow Token

update_connection

Modify Airflow connection parameters such as host, port, credentials, or schema by specifying the connection ID to maintain data pipeline configurations.

Instructions

Update a connection by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
conn_idYes
conn_typeNo
hostNo
portNo
loginNo
passwordNo
schemaNo
extraNo

Implementation Reference

  • Registers the update_connection tool (along with other connection tools) in the get_all_functions list used for MCP tool registration.
    def get_all_functions() -> list[tuple[Callable, str, str, bool]]:
        """Return list of (function, name, description, is_read_only) tuples for registration."""
        return [
            (list_connections, "list_connections", "List all connections", True),
            (create_connection, "create_connection", "Create a connection", False),
            (get_connection, "get_connection", "Get a connection by ID", True),
            (update_connection, "update_connection", "Update a connection by ID", False),
            (delete_connection, "delete_connection", "Delete a connection by ID", False),
            (test_connection, "test_connection", "Test a connection", True),
        ]
  • The main handler function for the update_connection tool. It constructs an update request from the provided parameters and calls the Airflow ConnectionApi to patch the connection.
    async def update_connection(
        conn_id: str,
        conn_type: Optional[str] = None,
        host: Optional[str] = None,
        port: Optional[int] = None,
        login: Optional[str] = None,
        password: Optional[str] = None,
        schema: Optional[str] = None,
        extra: Optional[str] = None,
    ) -> List[Union[types.TextContent, types.ImageContent, types.EmbeddedResource]]:
        update_request = {}
        if conn_type is not None:
            update_request["conn_type"] = conn_type
        if host is not None:
            update_request["host"] = host
        if port is not None:
            update_request["port"] = port
        if login is not None:
            update_request["login"] = login
        if password is not None:
            update_request["password"] = password
        if schema is not None:
            update_request["schema"] = schema
        if extra is not None:
            update_request["extra"] = extra
    
        response = connection_api.patch_connection(
            connection_id=conn_id, update_mask=list(update_request.keys()), connection_request=update_request
        )
        return [types.TextContent(type="text", text=str(response.to_dict()))]
Behavior2/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 states 'update' implies a mutation, but fails to describe what gets updated (e.g., fields like host, port), whether changes are reversible, permission requirements, or error handling. This leaves significant gaps in understanding the tool's behavior.

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

Conciseness4/5

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

The description is a single, efficient sentence with no wasted words, making it front-loaded and easy to parse. However, its brevity leads to under-specification, as it omits necessary details for a tool with 8 parameters.

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 8 parameters, 0% schema coverage, no annotations, and no output schema, the description is inadequate. It lacks details on what fields can be updated, expected outcomes, error conditions, and how it differs from related tools, making it incomplete for effective agent 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?

Schema description coverage is 0%, meaning parameters are undocumented in the schema. The description only mentions 'by ID', referencing the 'conn_id' parameter, but ignores the other 7 parameters (e.g., conn_type, host, password). It adds minimal value beyond the schema, failing to compensate for the coverage gap.

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 'Update a connection by ID' restates the tool name and title (which is null) without providing specific details about what 'update' entails. It mentions the resource (connection) and key parameter (ID), but lacks differentiation from sibling tools like 'create_connection' or 'delete_connection', making it vague about the exact operation.

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 is provided on when to use this tool versus alternatives. The description does not mention prerequisites (e.g., needing an existing connection ID), exclusions, or comparisons to sibling tools like 'create_connection' for new connections or 'delete_connection' for removal, leaving usage unclear.

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/nikhil-ganage/mcp-server-airflow-token'

If you have feedback or need assistance with the MCP directory API, please join our Discord server