Skip to main content
Glama
nikhil-ganage

MCP Server Airflow Token

get_pools

Retrieve and list available pools from Apache Airflow deployments to manage task execution resources and monitor capacity.

Instructions

List pools

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo
order_byNo

Implementation Reference

  • The handler function implementing the 'get_pools' tool. It accepts optional parameters for pagination and sorting, calls the Airflow PoolApi.get_pools, and returns the response as text content.
    async def get_pools(
        limit: Optional[int] = None,
        offset: Optional[int] = None,
        order_by: Optional[str] = None,
    ) -> List[Union[types.TextContent, types.ImageContent, types.EmbeddedResource]]:
        """
        List pools.
    
        Args:
            limit: The numbers of items to return.
            offset: The number of items to skip before starting to collect the result set.
            order_by: The name of the field to order the results by. Prefix a field name with `-` to reverse the sort order.
    
        Returns:
            A list of pools.
        """
        # Build parameters dictionary
        kwargs: Dict[str, Any] = {}
        if limit is not None:
            kwargs["limit"] = limit
        if offset is not None:
            kwargs["offset"] = offset
        if order_by is not None:
            kwargs["order_by"] = order_by
    
        response = pool_api.get_pools(**kwargs)
        return [types.TextContent(type="text", text=str(response.to_dict()))]
  • The get_all_functions() that provides the registration tuple for 'get_pools' tool, used by the main server to register it.
    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:90-92 (registration)
    The generic registration loop in main.py that adds the 'get_pools' tool (imported via get_pool_functions) to the MCP app using app.add_tool.
    for func, name, description, *_ in functions:
        app.add_tool(func, name=name, description=description)
  • src/main.py:15-15 (registration)
    Import of pool module's get_all_functions in main.py, enabling registration of get_pools tool.
    from src.airflow.pool import get_all_functions as get_pool_functions
Behavior1/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 but offers none. 'List pools' doesn't indicate whether this is a read-only operation, what permissions are required, whether it supports pagination (though parameters suggest it), what format the output takes, or any rate limits. For a tool with 3 parameters and no annotations, this is critically insufficient.

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 is extremely concise at just two words. While this leads to severe under-specification, it is not verbose or poorly structured—every word serves a purpose (though that purpose is minimal). There is no wasted language, making it technically efficient in terms of brevity.

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

Completeness1/5

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

Given the complexity (3 parameters, no annotations, no output schema, and many sibling tools), the description is completely inadequate. It doesn't explain what 'pools' are, how to use the parameters, what the tool returns, or when to choose it over alternatives. For a list operation in a system with extensive sibling tools, this provides almost no useful context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 0%, meaning none of the 3 parameters (limit, offset, order_by) are documented in the schema. The description 'List pools' adds no information about these parameters—it doesn't mention pagination, sorting, or any constraints. With 3 undocumented parameters and no compensation in the description, this fails to provide meaningful parameter semantics.

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 'List pools' is a tautology that essentially restates the tool name 'get_pools'. While it indicates a listing operation, it provides no additional specificity about what 'pools' are in this context or what distinguishes this tool from sibling tools like 'get_pool' (singular). The verb+resource combination is minimal and lacks differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides absolutely no guidance on when to use this tool versus alternatives. There is no mention of context, prerequisites, or comparisons to sibling tools like 'get_pool' (which presumably retrieves a single pool) or 'post_pool'/'patch_pool' (which create/modify pools). The agent receives no help in selecting this tool appropriately.

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