Skip to main content
Glama
mergestorm-mcp

mergestorm-mcp

Official

Get merge queue status

queue_status
Read-onlyIdempotent

Lists live merge queue entries and newest bounced entries with bounce details for the current user, optionally filtered by stack.

Instructions

List live merge queue entries (position >= 1) plus the newest bounced entries (position 0) with bounceDetail for the current user, optionally filtered by stack.

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

Input Schema

NameRequiredDescriptionDefault
stack_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.31

TDQS

B3.3/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 is covered. The description does add domain-specific behavior beyond those annotations: the position>=1 vs position 0 split and the presence of bounceDetail, plus current-user scoping. It still omits ordering, result size, and pagination behavior.

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?

A single dense sentence with no filler, front-loading the main content (live entries) before the secondary content (bounced entries) and the optional filter. Parenthetical position thresholds are compact and informative.

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

Completeness3/5

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

With no output schema, the description must convey return shape, and it partially does via position thresholds and bounceDetail. It leaves gaps on ordering ('newest' is only applied to bounced entries), result limits, and whether the live entries are sorted by position, which an agent would need to use the output 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 is one parameter with 0% schema description coverage, so the description must carry its meaning. It does: 'optionally filtered by stack' explains that stack_id narrows the result and is not required, which the schema alone does not convey beyond the type.

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?

The description names a specific verb and resource ('List live merge queue entries') and defines scope precisely: position >= 1 entries plus newest bounced position 0 entries with bounceDetail, scoped to the current user. It is clear what the tool returns, though it does not distinguish itself from siblings such as stack_status or stack_wait.

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?

There is no explicit when-to-use guidance, no statement of when not to use it, and no named alternative among the many stack/review status siblings. The only usage signal is the implicit 'current user' scoping and the optional stack filter.

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