Skip to main content
Glama

AgentMart

by ai.ciphyr.agentmart
OverviewDiscussionsAdmin

Return queue messages for a retry

queue_nack

Not done: the messages go back to the queue after delay_seconds, or to the dead-letter list after max_attempts claims.

Input Schema

NameRequiredDescriptionDefault
errorNoYour short reason.
queueYesQueue name: 1 to 64 characters from a-z 0-9 . _ -.
leasesYesLeases 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
    • 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."
  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

A3.6/5.0
Behavior4/5

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

Annotations only mark it as a non-read-only, non-destructive mutation; the description adds the substantive routing behavior — requeue after delay_seconds versus routing to the dead-letter list once max_attempts claims are exceeded. What is still missing is lease-validity failure behavior and whether error text is persisted, but the core behavioral consequence is disclosed.

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 short sentence with the outcome front-loaded and no filler. The terse "Not done:" fragment is economical but slightly cryptic as an opener.

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?

For a 6-parameter mutation with no output schema, the description covers the essential post-call state (retry queue vs dead-letter). It omits what happens with stale or already-expired leases and whether the error string is recorded, which an agent would need when a nack fails.

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 coverage is 100%, so buy/list_utilities, lease format and the delay window are already documented in the schema. The description only re-expresses delay_seconds' effect and introduces max_attempts, which is a queue setting rather than a parameter of this call, so it adds little beyond structured data. Baseline 3.

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?

"Not done: the messages go back to the queue" states the negative-acknowledgment semantics and the outcome, so an agent can tell this is the counterpart to queue_ack. However the actual verb (release/return) only appears in the title, and the description never plainly says "return claimed messages."

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

Usage Guidelines3/5

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

The opening "Not done" implies the condition for use (you failed to process the message), but no alternative is named — queue_ack, queue_extend and queue_dead are siblings in the same family and none are referenced. Usage is inferable rather than stated.

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

All AgentMart toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources