Skip to main content
Glama

get_queue_stats

Read-onlyIdempotent

Retrieve live merge queue depth for a repo—queued, processing, and waiting PR counts—to monitor backlog and diagnose delays.

Instructions

Live queue depth for a repo: queued, processing and waiting PR counts.

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": "get_queue_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgNoGitHub org. Optional if repo is 'org/name'.
repoNoGitHub repo name or 'org/name'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile needs no restating. The one genuinely additive piece is 'Live', which signals a non-cached, real-time read, but nothing is said about rate limits, auth scopes, or staleness/freshness guarantees beyond that word.

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?

One sentence, front-loaded with the core concept, with the three counted categories listed after the colon. Every clause carries information and there is no boilerplate.

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?

For a simple read-only metric tool with no output schema, the description effectively conveys the return shape (three integer PR counts). It falls short only on the distinction between 'queued' and 'waiting', which an agent may need to interpret the results correctly.

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

Parameters3/5

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

Schema coverage is 100% and both parameters (org, repo) are documented inline, including the 'org/name' fallback for org. The description adds only that the operation is scoped to a repo, so the baseline 3 applies — the schema does the heavy lifting.

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 resource ('Live queue depth for a repo') and enumerates exactly what is counted: queued, processing and waiting PRs. An agent can distinguish this from list_queued_prs or queue_pr by the fact that it returns counts, not PR records, though it never names those siblings explicitly.

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?

Usage is implied rather than stated: 'queue depth' suggests a status/overview check rather than an action, and the lack of any alternative or exclusion leaves the agent to infer that it should call list_queued_prs when it needs the actual PRs instead of counts.

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