Skip to main content
Glama

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, for workers to take with queue_claim. The queue is made on first use (60 s lease, 5 attempts; queue_settings changes them). All or nothing: if one message does not fit, none is added. Returns each message's id (a dedup_key already in the queue returns that message, duplicate: true). To store one value instead, use locker_put.

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",
      "messages": [
        {
          "body": {
            "file": "photo.png",
            "task": "resize"
          }
        }
      ],
      "instance_id": "que_exampleexampleexample2"
    },
    "name": "queue_put"
  }
}

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.6/5.0
Behavior4/5

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

Goes well beyond the annotations: auto-creation of the queue on first use, default 60 s lease and 5 attempts, and the all-or-nothing atomicity guarantee ("if one message does not fit, none is added") are all disclosed. Per-message 64 KB limit and the dedup/duplicate:true return behavior add further operational context. It does not contradict idempotentHint=false, since dedup only applies when a dedup_key is supplied.

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-loads the core action and limits, then layers in lifecycle, atomicity, return shape, and the sibling alternative. Every sentence carries distinct information with no restatement of the title.

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?

With no output schema, the description still explains what comes back (each message's id, plus duplicate:true for a recycled dedup_key). Failure semantics are summarized as all-or-nothing but the actual error shape is not described, a minor gap for a 4-parameter write tool.

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 adds the 64 KB per-message ceiling that the schema does not express, and ties messages to the queue/claim workflow. It does not re-explain queue naming or delay_seconds, which the schema already covers.

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 with capacity bounds ("Put 1 to 100 messages ... in a queue") and immediately scopes the audience ("for workers to take with queue_claim"), which separates it cleanly from locker_put and the claim/ack family.

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 the consuming tool (queue_claim), the configuration tool (queue_settings for lease/attempts), and the explicit alternative for a different job ("To store one value instead, use locker_put"). When-to-use and when-not-to-use are both covered.

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.