Skip to main content
Glama
astronomer

astro-airflow-mcp

Official
by astronomer

list_pools

Retrieve all configured resource pools with slot counts, occupancy, and capacity to manage task concurrency and resource allocation.

Instructions

Get resource pools for managing task concurrency and resource allocation.

Use this tool when the user asks about:

  • "What pools are configured?" or "List all pools"

  • "Show me the resource pools" or "What pools exist?"

  • "How many slots does pool X have?" or "What's the pool capacity?"

  • "Which pools are available?" or "What's the pool configuration?"

Pools are used to limit parallelism for specific sets of tasks. Each pool has a certain number of slots, and tasks assigned to a pool will only run if there are available slots. This is useful for limiting concurrent access to resources like databases or external APIs.

Returns pool information including:

  • name: Name of the pool

  • slots: Total number of available slots in the pool

  • occupied_slots: Number of currently occupied slots

  • running_slots: Number of slots with running tasks

  • queued_slots: Number of slots with queued tasks

  • open_slots: Number of available slots (slots - occupied_slots)

  • description: Human-readable description of the pool's purpose

Returns: JSON with list of all pools and their current utilization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations are provided, but the description fully discloses that this is a read-only list operation. It describes the returned fields and their meanings, and implies no side effects.

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 well-structured: a summary line, usage examples, a brief explanation of the resource, and a clear list of return fields. Every sentence is informative and concise.

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

Completeness5/5

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

Given no parameters and an output schema present, the description provides sufficient detail about the return fields and overall purpose. It covers what an agent needs to know to use this tool correctly.

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?

There are zero parameters, so the description cannot add parameter semantics. The baseline is 4 per guidelines, and the description does not need to elaborate further.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Get resource pools' and immediately lists example user questions. It is specific to listing all pools, which distinguishes it from get_pool (singular).

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

Usage Guidelines5/5

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

Explicitly lists when to use the tool with example questions. Also explains the concept of pools and their purpose, giving context for appropriate 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/astronomer/astro-airflow-mcp'

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