Skip to main content
Glama

list_pools

Retrieve all available pools from Airflow to manage task execution resources and monitor cluster capacity.

Instructions

[Tool Role]: Lists all pools in Airflow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function for the 'list_pools' tool. It makes an API request to the Airflow pools endpoint with pagination parameters and returns the response.
    @mcp.tool()
    async def list_pools(limit: int = 20, offset: int = 0) -> Dict[str, Any]:
        """[Tool Role]: Lists all pools in Airflow."""
        params = {'limit': limit, 'offset': offset}
        query_string = "&".join([f"{k}={v}" for k, v in params.items()])
        resp = await airflow_request("GET", f"/pools?{query_string}")
        resp.raise_for_status()
        return resp.json()
  • Registration of common tools (including list_pools) for Airflow API v1 by calling register_common_tools after setting v1-specific airflow_request.
    common_tools.register_common_tools(mcp)
  • Registration of common tools (including list_pools) for Airflow API v2 by calling register_common_tools after setting v2-specific airflow_request.
    common_tools.register_common_tools(mcp)
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits such as pagination behavior (implied by limit/offset but not explained), authentication needs, rate limits, or what 'all pools' entails (e.g., active/inactive).

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 a single, efficient sentence with no wasted words. It's front-loaded with the core action, making it easy to scan and understand quickly.

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's low complexity (list operation with pagination), no annotations, and an output schema (which handles return values), the description is minimally adequate. However, it lacks context on usage scenarios or behavioral details that would enhance completeness.

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 description coverage is 0%, but the description doesn't add any parameter information beyond what's inferred from the schema (limit and offset for pagination). The baseline is 3 because the schema provides the parameters, but the description doesn't compensate for the lack of schema descriptions.

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 clearly states the verb ('Lists') and resource ('all pools in Airflow'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'get_pool' or other list_* tools, which would require specifying scope or uniqueness.

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_pool' (for a specific pool) or other list_* tools. The description only states what it does, not when it's appropriate.

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