Skip to main content
Glama
yangkyeongmo

MCP Server for Apache Airflow

by yangkyeongmo

get_pool

Retrieve a specific connection pool by name from Apache Airflow to manage database or resource connections within workflow orchestrations.

Instructions

Get a pool by name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pool_nameYes

Implementation Reference

  • The handler function that implements the core logic of the 'get_pool' tool. It takes a pool_name parameter, calls the Airflow PoolApi to retrieve the pool, and returns the details as TextContent.
    async def get_pool(
        pool_name: str,
    ) -> List[Union[types.TextContent, types.ImageContent, types.EmbeddedResource]]:
        """
        Get a pool by name.
    
        Args:
            pool_name: The pool name.
    
        Returns:
            The pool details.
        """
        response = pool_api.get_pool(pool_name=pool_name)
        return [types.TextContent(type="text", text=str(response.to_dict()))]
  • The get_all_functions utility that provides the registration tuple for the 'get_pool' tool, including the function reference, name, description, and read-only flag.
    def get_all_functions() -> list[tuple[Callable, str, str, bool]]:
        """Return list of (function, name, description, is_read_only) tuples for registration."""
        return [
            (get_pools, "get_pools", "List pools", True),
            (get_pool, "get_pool", "Get a pool by name", True),
            (delete_pool, "delete_pool", "Delete a pool", False),
            (post_pool, "post_pool", "Create a pool", False),
            (patch_pool, "patch_pool", "Update a pool", False),
        ]
  • src/main.py:16-16 (registration)
    Import of the pool module's get_all_functions (aliased as get_pool_functions) used for registering pool-related tools including 'get_pool'.
    from src.airflow.pool import get_all_functions as get_pool_functions
  • src/main.py:35-35 (registration)
    Mapping of APIType.POOL to get_pool_functions, which enables the registration of the 'get_pool' tool during server startup.
    APIType.POOL: get_pool_functions,
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 burden of behavioral disclosure. It states 'Get a pool by name,' implying a read operation, but doesn't clarify if this requires authentication, returns specific data formats, handles errors (e.g., if the pool doesn't exist), or has rate limits. This leaves significant gaps for an agent to understand how to invoke it safely and effectively.

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 'Get a pool by name' is extremely concise and front-loaded, with no wasted words. It efficiently conveys the core action in a single phrase, making it easy for an agent to parse and understand quickly.

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?

Given the tool's simplicity (1 parameter, no output schema, no annotations), the description is incomplete. It lacks details on behavioral aspects (e.g., error handling, authentication), parameter specifics, and how it differs from siblings like 'get_pools'. For a read operation in a server with many tools, more context would help an agent use it correctly.

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 ('pool_name') with 0% description coverage, meaning the schema provides no details about this parameter. The description adds minimal semantics by implying 'pool_name' is used to look up a pool, but doesn't specify format, constraints, or examples. Since schema coverage is low, the description partially compensates but not fully, warranting a baseline score.

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?

The description 'Get a pool by name' clearly states the verb ('Get') and resource ('pool'), and specifies the lookup method ('by name'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'get_pools' (plural) or 'patch_pool', leaving room for confusion about when to use this versus alternatives.

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 like 'get_pools' (which likely lists multiple pools) or 'patch_pool' (which modifies pools). The description implies it's for retrieving a single pool by name, but lacks explicit context or exclusions, such as whether it's for read-only access or requires specific permissions.

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/yangkyeongmo/mcp-server-apache-airflow'

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