Skip to main content
Glama

Return queue messages for a retry

queue_nack

Return claimed messages for a retry (not done): each lease from queue_claim puts its message back in the queue, claimable after delay_seconds (default 0), or in the dead letters (queue_dead) once it used the queue's max_attempts claims. Returns requeued, dead_lettered and lost (leases that matched nothing). Use queue_ack when done, queue_extend for more time.

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": {
      "queue": "jobs",
      "leases": [
        "lse_0123456789abcdef0123456789abcdef"
      ],
      "instance_id": "que_exampleexampleexample2",
      "delay_seconds": 60
    },
    "name": "queue_nack"
  }
}

Input Schema

NameRequiredDescriptionDefault
errorNoYour short reason (queue_dead shows it as last_error).
queueYesQueue name: 1 to 64 characters from a-z 0-9 . _ -.
leasesYesLeases (lse_...) from queue_claim.
instance_idYesUtility instance id from buy or list_utilities.
delay_secondsNoWait this long before it can be claimed again.
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
    • changedInput schema / properties / error / description
      Previous value: -"Your short reason."New value: +"Your short reason (queue_dead shows it as last_error)."
    • changedInput schema / properties / leases / description
      Previous value: -"Leases from queue_claim."New value: +"Leases (lse_...) from queue_claim."
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "delay_seconds": 60,
      +    "instance_id": "que_exampleexampleexample2",
      +    "leases": [
      +      "lse_0123456789abcdef0123456789abcdef"
      +    ],
      +    "queue": "jobs"
      +  }
      +]
    • 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."
  3. 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}$"
  4. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare not-read-only, not-idempotent and non-destructive; the description goes well beyond that by explaining the state machine: message requeues after delay_seconds (default 0), or lands in dead letters once max_attempts is exhausted. It also discloses the return buckets including 'lost' leases that matched nothing, which is real behavioral context an agent cannot get from the annotations.

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?

Two sentences, front-loaded with the core action, then consequences, then sibling routing. Dense with parentheticals but every clause carries information; slight cost in readability from packing requeue, dead-letter and lost into one sentence.

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?

No output schema exists, yet the description enumerates the three result buckets (requeued, dead_lettered, lost) so the agent knows what comes back. For a 6-parameter mutation tool with a retry/delay/dead-letter lifecycle, nothing needed for correct invocation is missing.

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 baseline is 3, but the description still adds meaning: it supplies the default for delay_seconds (0) and ties leases to their origin in queue_claim, which the schema text does not do. The max_attempts interaction gives dead-lettering semantics that no single parameter description carries.

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?

States a specific verb and resource ('Return claimed messages for a retry') plus an explicit negation ('not done') that separates it from queue_ack. The clause 'each lease from queue_claim puts its message back in the queue' anchors it against the claim sibling.

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?

Names both alternatives and the condition selecting each: 'Use queue_ack when done, queue_extend for more time.' It states implicitly when this tool is the right one (retry after incomplete work) and explicitly routes the other two cases away.

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.