Skip to main content
Glama

AgentMart

by ai.ciphyr.agentmart
OverviewDiscussionsAdmin

Put messages in my queue

queue_put

Put 1 to 100 messages (any JSON, up to 64 KB each) in a queue of your durable-queue plan; the queue is made on first use. dedup_key: while a message with it is in the queue, the same key returns that message.

Input Schema

NameRequiredDescriptionDefault
queueYesQueue name: 1 to 64 characters from a-z 0-9 . _ -.
messagesYesThe messages to put.
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. Changed4 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "instance_id": "que_exampleexampleexample2",
+    "messages": [
+      {
+        "body": {
+          "file": "photo.png",
+          "task": "resize"
+        }
+      }
+    ],
+    "queue": "jobs"
+  }
+]
    • addedInput schema / properties / messages / items / properties / dedup_key / description
      Added value: +"While a message with this key is in the queue (dead letters too), another put with it returns that message (duplicate: true)."
    • addedInput schema / properties / messages / items / properties / delay_seconds / description
      Added value: +"0 to 900 (15 minutes): claimable only after this. Default 0."
    • 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/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent behavior, and the description adds genuine context beyond that: the queue is auto-created on first use, message size limits, and the fact that a repeated dedup_key returns the existing message rather than enqueuing a duplicate. It stops short of describing failure modes or whether queued messages are immediately claimable, so it is strong but not exhaustive.

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?

Two tight clauses, front-loaded with the action and its limits before the dedup nuance. Nothing is wasted and there is no filler.

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

Completeness4/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 voluntarily covers the notable return case (dedup returns the existing message). Combined with complete schema coverage and safety annotations, this is nearly sufficient; only error/edge behavior on enqueue is unaddressed.

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 the schema already documents queue naming, dedup_key, delay_seconds, and passport_token. The description restates the dedup_key semantics rather than adding new format or constraints, so baseline 3 applies.

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 (put) plus the resource (messages in a durable queue) and immediately bounds the payload size and count (1-100 messages, 64 KB each). This clearly separates it from siblings like queue_claim, queue_ack, or locker_put without needing the schema.

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 description implies this is the enqueue step but never says when to use it over alternatives such as queue_claim or locker_put, nor does it mention prerequisites beyond 'a durable-queue plan'. Usage must be inferred from the verb and the plan mention.

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