Skip to main content
Glama

queue_status

Resolve communication delays between AI assistants by checking queue counts and reviewing recent completions for debugging.

Instructions

Return queue counts + recent completions (debugging).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual MCP tool handler for queue_status. Defined as a synchronous function returning a dict, decorated with @mcp.tool(). It delegates to _queue.status() which returns queue counts and recent completions.
    @mcp.tool()
    def queue_status() -> dict:
        """Return queue counts + recent completions (debugging)."""
        return _queue.status()
  • The status() method on MessageQueue, which is the backing logic that queue_status calls. It counts JSON files in pending/inflight/done/failed subdirectories and returns the 5 most recent done message IDs.
    def status(self) -> dict:
        def _count(sub: str) -> int:
            return len(list((self.base / sub).glob("*.json")))
    
        recent_done = sorted(
            (self.base / "done").glob("*.json"),
            key=lambda p: p.stat().st_mtime,
            reverse=True,
        )[:5]
        return {
            "mode": self.mode,
            "base": str(self.base),
            "pending": _count("pending"),
            "inflight": _count("inflight"),
            "done": _count("done"),
            "failed": _count("failed"),
            "recent_done_ids": [p.stem for p in recent_done],
        }
  • The @mcp.tool() decorator registers queue_status as an MCP tool on the FastMCP instance named 'mcp' (line 52). This is the registration mechanism that makes it discoverable.
    @mcp.tool()
  • The Message dataclass used by MessageQueue to store individual messages. queue_status aggregates these messages into counts.
    @dataclass
    class Message:
        id: str
        from_agent: str
        to_agent: str
        question: str
        created_at: float
        priority: int = 1
        timeout: int = 300
        answer: Optional[str] = None
        completed_at: Optional[float] = None
        failed_reason: Optional[str] = None
Behavior4/5

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

No annotations are provided, but the description clearly indicates it is a non-destructive read (returning counts and completions). There is no behavior beyond what is described, and no contradictions. A slight deduction for not explicitly stating read-only nature.

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 immediately states the tool's purpose and context. No fluff or redundant information.

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?

Given zero parameters and no output schema, the description sufficiently describes the tool's output. It could be considered complete for a simple status check, though mentioning any authentication or availability requirements would improve completeness.

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 input schema has no parameters (0 params, 100% coverage). The description adds value by specifying the return content (queue counts + recent completions). Baseline 4 is appropriate since the schema carries no burden.

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 tool returns queue counts and recent completions, with 'debugging' context. It identifies the specific resource (queue status) and verb (return). It is well distinguished from siblings like ask_claude, ask_codex, and broadcast.

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

Usage Guidelines3/5

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

The description implies usage for debugging via the parenthetical '(debugging)'. It does not explicitly state when to use vs. alternatives or when not to use, but the siblings are sufficiently different, so the guidance is adequate but minimal.

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/jonghklee/teammate-mcp'

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