Skip to main content
Glama

Add a task to a loop

enqueue_task

Append one of the user's tasks to the end of a loop's 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": {
      "loop_id": "<loop_id>",
      "task_id": "<task_id>"
    },
    "name": "enqueue_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
loop_idYesThe loop's id (from list_loops).
task_idYesThe task's id (from list_tasks, todays_tasks or a loop's tasks).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuine context by stating the task is appended to the *end* of the queue, implying ordering matters and repeats may be possible — but it says nothing about duplicate handling, task state changes, or failure conditions.

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?

A single front-loaded sentence with no filler; the resource and the queue position are both stated immediately.

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?

For a two-parameter, fully documented mutation with a complete annotation set and no output schema, this is close to sufficient. The remaining gap is eligibility and duplicate semantics for a non-idempotent enqueue, which would be worth one more clause.

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% and both parameters already carry descriptions naming their source endpoints (list_loops, list_tasks, todays_tasks). The description only adds the qualifier 'one of the user's tasks', which does not extend meaning 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?

States a specific verb (append) and both resources (a user task, a loop's queue), plus the positional detail that it goes to the end of the queue. That distinguishes it from dequeue_task and create_task, though it doesn't name or route away from any sibling explicitly.

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 when-to-use or when-not-to-use guidance, no prerequisites (e.g. task must exist, loop must be active), and no mention of how this differs from create_task or arm_all. The agent must infer eligibility entirely from the one-line action statement.

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