Skip to main content
Glama

loop_task_enqueue

Enqueue durable, idempotent tasks into a shared SQLite WAL queue so workflows can safely schedule work and resume after interruptions without duplicate execution.

Instructions

Enqueue an idempotent durable task into the shared SQLite WAL queue.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "task_id": "<task_id>",
      "verb": "<verb>",
      "payload": "<payload>"
    },
    "name": "loop_task_enqueue"
  }
}

Input Schema

NameRequiredDescriptionDefault
verbYes
payloadYes
task_idYes
namespaceNo
contract_digestNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose genuinely useful traits: the operation is idempotent, tasks are durable, and storage is a shared SQLite WAL queue, which tells an agent a retry with the same task_id is safe. However it is silent on what a duplicate enqueue returns, whether the call blocks or fails on a locked WAL, permission requirements, and the response shape (no output schema).

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 front-loaded sentence with no filler or redundancy. It is efficient, though the brevity is a consequence of under-specification rather than disciplined editing, so it does not reach a 5.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a state-mutating write tool with five parameters, a nested object, zero schema coverage, and no annotations or output schema, one sentence is not sufficient. An agent still cannot tell what verb values are legal, what goes in payload, or what happens on a duplicate or failed enqueue.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters, including a nested payload object, so the description must compensate and largely does not. The only indirect hint is that 'idempotent' implies task_id acts as the deduplication key. The meaning and expected shape of verb, payload, namespace, and contract_digest are left entirely undocumented.

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 description states a specific verb (enqueue) and resource (durable task) and adds qualifying scope: idempotent, durable, shared SQLite WAL queue. This is well beyond a tautology. It stops short of naming or contrasting the siblings loop_task_claim or loop_task_checkpoint, so an agent must infer the relationship itself.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no when-not guidance, and no mention of the claim/checkpoint/verify siblings as alternatives. A reader can infer that enqueueing precedes claiming, but that is entirely implicit and the description never says so.

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