Skip to main content
Glama

get_pool

Retrieve detailed information about a specific task execution pool in Apache Airflow to monitor resource allocation and optimize workflow management.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pool_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'get_pool' tool. It makes a GET request to the Airflow API endpoint `/pools/{pool_name}` to retrieve details for the specified pool. The @mcp.tool() decorator also serves as the registration point for this tool.
    async def get_pool(pool_name: str) -> Dict[str, Any]:
        """[Tool Role]: Gets details for a specific pool."""
        resp = await airflow_request("GET", f"/pools/{pool_name}")
        resp.raise_for_status()
        return resp.json()
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 'Gets details', implying a read-only operation, but doesn't specify if it requires authentication, what happens if the pool doesn't exist, or the format of returned details. For a tool with no annotation coverage, this leaves significant gaps in understanding its behavior.

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—a single sentence that directly states the tool's role. It's front-loaded with the core function and wastes no words, making it easy to parse quickly. This efficiency is appropriate for a simple retrieval tool.

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 an output schema (which should document return values) and only one parameter, the description is minimally adequate. However, with no annotations and low schema coverage, it lacks context on error handling, authentication, or data format, which could be important for a retrieval operation in this server environment.

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

Parameters4/5

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

The description adds meaningful context by specifying that it retrieves details for a 'specific pool', which clarifies the purpose of the 'pool_name' parameter beyond what the schema provides (schema coverage is 0%). However, it doesn't detail what constitutes a valid pool name or provide examples, leaving some ambiguity.

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 pool', which clearly indicates a read operation on a pool resource. However, it lacks specificity about what 'details' include and doesn't differentiate from sibling tools like 'list_pools' or 'get_dag' that might also retrieve pool-related information, making it somewhat vague.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, such as needing to know the pool name beforehand, or contrast it with 'list_pools' for browsing all pools. Without any usage context, the agent must infer this from the tool name and schema alone.

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