Skip to main content
Glama

Acknowledge queue messages (deletes them)

queue_ack
DestructiveIdempotent

Acknowledge messages claimed from the named queue: each lease from queue_claim permanently deletes its message. Use it when the job is done; on failure use queue_nack, for more time queue_extend. A lease that ran out still works until its message is claimed again, nacked, redriven or deleted. Returns acked, and lost for each lease that deleted nothing, not as an error. 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": {
      "queue": "jobs",
      "leases": [
        "lse_0123456789abcdef0123456789abcdef"
      ],
      "instance_id": "que_exampleexampleexample2"
    },
    "name": "queue_ack"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
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. Changed1 schema field changed
    • 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: +[
      +  {
      +    "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.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description goes beyond them: it explains lease expiry semantics (an expired lease still works until the message is re-claimed, nacked, redriven or deleted) and partial-failure behavior ("Returns acked, and lost for each lease that deleted nothing, not as an error"). That partial-success contract is exactly the kind of non-obvious trait an agent needs before calling a delete tool on a batch.

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?

Front-loaded with the destructive effect before any alternatives, then alternatives, then edge cases and return contract. Every sentence carries a distinct fact (delete semantics, failure routing, expired leases, partial results, post-plan behavior) with no filler.

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, and the description compensates by naming the return fields (acked, lost) and clarifying that partial outcomes are not errors. Combined with the expired-lease and post-plan caveats, it covers everything an agent needs to call this batch-delete 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 description coverage is 100%, so queue, leases, instance_id and passport_token are already documented in structured fields, and the description largely restates them. It reinforces that leases come from queue_claim and that missing ones surface in "lost" rather than as errors, but adds no syntax or format detail beyond the schema. 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?

States a specific verb and resource ("Acknowledge messages claimed from the named queue") and immediately names the effect ("each lease from queue_claim permanently deletes its message"). It distinguishes itself from queue_nack and queue_extend by name, so an agent can pick it without opening sibling schemas.

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?

Explicit routing: "Use it when the job is done; on failure use queue_nack, for more time queue_extend." It also names an edge case where a caller might wrongly assume the tool is unavailable ("Works after the plan ended"), which is genuine when-to-use guidance rather than inferred context.

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.