Skip to main content
Glama

Show my queues

queue_status
Read-only

Check the backlog of your durable queues: each one's live counts (ready, delayed, leased, dead, total, bytes) and settings. A lease that ran out counts as ready, or dead after max_attempts claims. Without queue: all queues, plus plan_bytes and plan_max_bytes. With queue: that queue, or queue_not_found. No message bodies: queue_claim takes work, queue_dead lists dead letters. Works after the plan ended.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "instance_id": "que_exampleexampleexample2"
    },
    "name": "queue_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
queueNoOnly this queue, with its settings.
instance_idYesUtility instance id from buy or list_utilities.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "instance_id": "que_exampleexampleexample2"
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  2. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  3. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already establish the safe read-only, closed-world profile, so the description is free to add semantics that structured fields cannot express: how expired leases are counted (ready, or dead after max_attempts), that plan_bytes/plan_max_bytes accompany the all-queues listing, that message bodies are excluded, and that it keeps working after the plan ended. These are non-obvious traits an agent would otherwise guess at.

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?

Six short sentences, each carrying distinct information, front-loaded with the returned counts before the conditional branches and the negative scoping. Nothing is repeated from the title or annotations.

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

Completeness5/5

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

There is no output schema, so the description carries the return-value burden and does so by listing the exact fields returned and the aggregate plan fields. Combined with the lease semantics and the not-found case, an agent has everything needed to call it and interpret results.

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?

Schema coverage is 100%, so the baseline is 3; the description earns a bump by explaining the observable effect of the queue filter and its not-found path, which the schema's 'Only this queue, with its settings' does not convey. It adds no format or length guidance, but none is needed.

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 opens with a specific verb and resource ('Check the backlog of your durable queues') and immediately enumerates what is returned (ready, delayed, leased, dead, total, bytes) plus settings. That is enough for an agent to distinguish it from queue_claim and queue_dead without consulting any schema.

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

Usage Guidelines5/5

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

It gives explicit conditional behavior for the optional parameter ('Without queue: all queues... With queue: that queue, or queue_not_found') and routes the agent to alternatives by naming queue_claim for taking work and queue_dead for dead letters. Both when-to-use and when-to-look-elsewhere are stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.