Skip to main content
Glama
Sign In
queue-inspector-mcp

queue-inspector-mcp

by Yusufihsangorgel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List queues

list_queues
Read-only

List all visible queues with their backend type (Asynq or BullMQ) to inspect job queue status.

Instructions

List every queue the inspector can see, tagged with its backend (asynq or bullmq).

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

Input Schema

NameRequiredDescriptionDefault
backendNoWhich backend owns the queue. Optional when the queue name is unique across backends.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so description's mention of 'the inspector can see' adds marginal value. Mention of backend tagging provides some output behavior detail but lacks disclosure of pagination, rate limits, or access restrictions.

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, well-structured sentence that immediately conveys the tool's action and key feature (backend tags). No extraneous text.

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?

Given no output schema, the description partially compensates by noting output includes backend tags, but doesn't specify other returned fields or structure. Adequate for a simple list tool but not fully complete.

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 has 100% description coverage for the single parameter 'backend' (with enum). Description adds no extra parameter semantics beyond schema, so baseline 3 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 tool lists every queue visible to the inspector, with a specific detail about tagging with backend type. This distinguishes from sibling tools focused on jobs or queue statistics.

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 on when to use this tool versus alternatives, such as queue_stats or other queue-related tools. The description only states functionality, not context of use.

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

Deploy Server

Other Tools