Skip to main content
Glama

get_connection

Retrieve connection configuration details from Apache Airflow clusters to manage data pipeline integrations and monitor connectivity settings.

Instructions

[Tool Role]: Gets details for a specific connection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
connection_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'get_connection' MCP tool. It makes a GET request to the Airflow API to retrieve details for a specific connection by its ID. The function is automatically registered as an MCP tool via the @mcp.tool() decorator.
    @mcp.tool()
    async def get_connection(connection_id: str) -> Dict[str, Any]:
        """[Tool Role]: Gets details for a specific connection."""
        resp = await airflow_request("GET", f"/connections/{connection_id}")
        resp.raise_for_status()
        return resp.json()
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 the tool 'Gets details,' implying a read-only operation, but does not disclose any behavioral traits such as authentication requirements, rate limits, error handling, or what the output contains. This leaves significant gaps for an agent to understand how to use it effectively.

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 concise with a single sentence that directly states the tool's role. It is front-loaded and wastes no words, though it could benefit from more detail to improve clarity and completeness without sacrificing brevity.

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?

Given the tool has 1 parameter with no schema descriptions and an output schema exists, the description is minimally adequate. It covers the basic purpose but lacks details on usage, behavior, and parameter semantics, leaving the agent to rely heavily on the output schema and potentially trial-and-error for full understanding.

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?

The input schema has 1 parameter with 0% description coverage, so the schema provides no semantic information. The description adds minimal value by implying 'connection_id' is needed to identify a specific connection, but it does not explain the format, source, or constraints of this ID. This partial compensation results in a baseline score due to low schema coverage.

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 tool 'Gets details for a specific connection,' which clearly indicates a read operation (verb 'Gets') on a resource ('connection'). However, it lacks specificity about what 'details' entail and does not differentiate from sibling tools like 'list_connections' or 'create_connection,' making it vague in comparison.

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. For example, it does not mention using 'list_connections' to find connection IDs first or when to prefer 'get_connection' over 'update_connection' or 'delete_connection.' The description offers no context or exclusions for usage.

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