Skip to main content
Glama

List resource pools

cron_list_pools
Read-onlyIdempotent

Shows each scheduler pool's capacity, queued work, and recent queue outcomes so you can diagnose jobs waiting on pool capacity and find queue entry IDs to cancel.

Instructions

Show each pool's capacity, queued work, and recent queue outcomes. Use it when jobs wait for pool capacity, or to find the queue entry ID that cron_cancel_queued takes when the act tools are on.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cron_list_pools"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value by disclosing what the response contains (capacity, queued work, recent outcomes) and its role as a prerequisite lookup for cron_cancel_queued — context annotations cannot carry. The trailing 'when the act tools are on' qualifier is left unexplained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with output content and then usage. No filler, though the final clause 'when the act tools are on' is cryptic and slightly undercuts the crispness of the routing guidance.

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

Completeness4/5

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

No output schema exists, so the one-line summary of returned fields (capacity, queued work, outcomes) is exactly the right compensation. Nothing about invocation is missing for a parameterless read tool; only the queue-entry-ID linkage to cron_cancel_queued could be spelled out more precisely.

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?

Zero parameters, so there is nothing for the description to disambiguate; baseline applies. The description correctly implies the tool is filter-free and returns all pools.

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?

States a specific verb and resource ('Show each pool's...') and enumerates what is returned: capacity, queued work, recent queue outcomes. That separates it from per-job siblings like cron_get_job_resources or cron_query_metrics, though it never names a sibling explicitly.

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

Usage Guidelines4/5

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

Gives two concrete triggers: 'when jobs wait for pool capacity' and 'to find the queue entry ID that cron_cancel_queued takes'. That is a real use-case-to-tool mapping, but there is no explicit when-not-to-use or contrast with the sibling list tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.