Skip to main content
Glama
Darius1223
by Darius1223

get_queue_lengths

Identify queue backlogs and balance task distribution by fetching real-time lengths of all Celery queues.

Instructions

Get the current length of all Celery queues.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The actual handler function for the 'get_queue_lengths' tool. It calls client.get('/api/queues/length'), logs the result, and returns the data as a JSON string.
    async def get_queue_lengths() -> str:
        """Get the current length of all Celery queues."""
        data = await client.get("/api/queues/length")
        logger.info("Fetched queue lengths")
        return json.dumps(data)
  • The 'register' function that decorates get_queue_lengths with @mcp.tool() to register it as an MCP tool.
    def register(mcp: FastMCP, client: FlowerClient) -> None:
        @mcp.tool()
  • source/main.py:25-25 (registration)
    Queues registration call in main lifespan: queues.register(mcp, client) wires up get_queue_lengths as an MCP tool.
    queues.register(mcp, client)
  • The FlowerClient.get() method used by the handler to make the HTTP GET request to the Flower API.
    async def get(self, path: str, params: dict[str, Any] | None = None) -> Any:
        logger.debug("GET {} params={}", path, params)
        resp = await self._client.get(path, params=params)
        resp.raise_for_status()
        if "application/json" in resp.headers.get("content-type", ""):
            return resp.json()
        try:
            return resp.json()
        except Exception:
            return resp.text
Behavior3/5

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

With no annotations, the description carries the full burden for behavioral disclosure. It states the basic function but omits any traits like read safety, expense, or freshness guarantees. The behavior is simple and expected, so it minimally meets the need.

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 sentence that immediately conveys the purpose. There is no fluff or unnecessary detail, making it highly concise and effective.

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?

The description is complete enough for a simple read-only query with no parameters and an output schema. It lacks minor context like the nature of Celery queues but is still functional.

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 tool has zero parameters and the schema coverage is 100%. The description does not need to add parameter details; the baseline is appropriate.

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 the action ('Get') and the resource ('current length of all Celery queues'), making it specific and distinct from sibling tools like 'list_tasks' or 'get_task_info'.

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, such as other queue-related tools or when the queue lengths might be stale. The description lacks any contextual cues 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/Darius1223/celery-flower-mcp'

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