Skip to main content
Glama

MCPFax Agent Continuity

Push work items onto a durable queue

work_push
Idempotent

THE ALTERNATIVE TO THIS IS WRITING DISTRIBUTED WORK-DISTRIBUTION CODE YOURSELF — assignment, collision avoidance, lease expiry, retry, dead-worker recovery, straggler policy. Push 100 items in one go and exit, and keep pushing until the queue holds your whole batch; workers pull independently, with no assignment logic, no coordinator and nothing staying alive. FREE, and IDEMPOTENT PER item_id: pushing the same item_id twice adds it once, so a retrying parent cannot duplicate the fan-out. Payloads are opaque and never parsed. FREE — this tool never charges. Authenticate with Authorization: Bearer , or pass agent_key as an argument if your host cannot set headers. Equivalent HTTP route: POST /v1/work/push.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesUp to 100 per call. Each entry is {item_id, payload} or a bare string used as the item_id. item_id <=128 chars, payload <=8192 bytes. A queue holds 2000 items over its LIFETIME, finished ones included, because work_status keeps their results and dead letters; over that, pushes are refused by name rather than dropped. Example: '[{"item_id":"P-1","payload":{"url":"..."}}]'.
queue_idYesYour name for this queue. Namespace-scoped: it belongs to the namespace that created it, and only a caller holding that agent_secret can push to or take from it. Example: 'permit-batch-2026-08'.
agent_keyNoYour agent_secret, if your MCP host cannot set the Authorization header. Prefer the header.
ttl_secondsNoQueue retention. Default 604800 (7d), max 2592000 (30d). Example: '604800'.
max_attemptsNoHow many times an item may be handed to a worker before it is dead-lettered. Default 3, max 20. Set on first push; later pushes do not change it. Example: '3'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / agent_key / examples
      Added value: +[
      +  "the agent_secret that register returned"
      +]
  2. Changed4 schema fields changed
    • addedInput schema / properties / items / examples
      Added value: +[
      +  "[{\"item_id\":\"P-1\",\"payload\":{\"url\":\"...\"}}]"
      +]
    • addedInput schema / properties / max_attempts / examples
      Added value: +[
      +  3
      +]
    • addedInput schema / properties / queue_id / examples
      Added value: +[
      +  "permit-batch-2026-08"
      +]
    • addedInput schema / properties / ttl_seconds / examples
      Added value: +[
      +  604800
      +]
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The description goes well beyond annotations: it specifies idempotency is per item_id, duplicate pushes add once, payloads are opaque and never parsed, authentication can be via Authorization header or agent_key, and the tool never charges. It does not contradict the annotations, though it omits response/failure behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is written in all-caps marketing voice, repeats 'FREE' twice, and buries authentication near the end. It contains useful information but is not appropriately sized or front-loaded for an MCP tool definition.

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?

Combined with the 100% parameter schema and annotations, the description covers batching, repeated pushing, idempotency, opaque payloads, auth, and the no-coordinator model. It does not describe return values or explicitly point to consumer siblings like work_take, but those are minor gaps for this 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 value by explaining agent_key usage context, idempotency semantics for item_id, and that payloads are opaque, which enriches the meaning of the items parameter beyond the schema.

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?

The title and description clearly state the operation: enqueue work items onto a durable queue, with a concrete usage pattern of pushing up to 100 items and repeating until the batch is queued. It does not explicitly distinguish from sibling tools like work_take, though the push/pull split is obvious from names.

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

Usage Guidelines4/5

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

The description explains when to use this tool: instead of writing custom work-distribution code, push items and let workers pull independently. It gives a clear usage pattern and mentions idempotency for retrying parents, but it does not explicitly say 'do not use for pulling' or name sibling alternatives.

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.

Resources