Skip to main content
Glama
MCP-Airflow-API

MCP-Airflow-API

by call518

get_connection

Retrieve details for a specific Airflow connection using its exact connection ID, so you can inspect connection configuration without handling Airflow API complexity.

Instructions

[Tool Role]: Gets details for a specific 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": "get_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.9/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 disclosure burden and does almost nothing with it: it does not say whether the read is safe, whether sensitive fields (e.g. passwords in the connection) are masked, what happens when the ID does not exist, or what permissions are needed.

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?

One short, front-loaded sentence with no waste; the '[Tool Role]:' prefix is mild boilerplate but harmless. It errs toward under-specification rather than verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and the sole parameter is documented, so the essentials for calling the tool are covered. Still missing is how an agent should obtain a valid connection_id (e.g. via list_connections) and the not-found behavior.

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 coverage is 100% and the single connection_id parameter is described as the 'Exact Airflow connection identifier', so the schema does the work. The description adds nothing about the parameter, so the baseline 3 applies.

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

Purpose4/5

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

States a specific verb ('Gets details') and resource ('a specific connection'), and the singular framing plus the required connection_id distinguishes it from the plural list_connections sibling. What the 'details' actually encompass is left unspecified, keeping it short of a 5.

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 explicit statement of when to use this versus list_connections or the create/update/delete_connection siblings; the distinction only exists implicitly in the tool name and the required ID parameter.

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