Skip to main content
Glama

Remove a task from a loop

dequeue_task
DestructiveIdempotent

Remove a task from a loop's queue (the task itself is kept).

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": "dequeue_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

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, but the description adds the crucial scoping fact that the task record survives the operation — telling the agent exactly how far the 'destruction' extends. It does not say what happens when the task is not queued or whether queue order is affected.

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 a parenthetical that earns its place by disambiguating against deletion. 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?

For a two-parameter tool with full schema coverage and complete annotations, the definition covers the essential semantic risk (task preserved). Only edge-case behavior — error when the task is absent from the queue, effect on ordering — is left unstated.

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 description coverage is 100% and both parameters already name their source lists (list_loops, list_tasks/todays_tasks), so the description adds nothing beyond the schema. Baseline 3 is appropriate.

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?

Names a specific verb and resource ('Remove a task from a loop's queue') and the parenthetical '(the task itself is kept)' distinguishes it from a full deletion, which matters given a sibling named delete_task. It stops short of naming the counterpart enqueue_task directly.

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?

Usage is implied rather than stated: un-queuing is the inverse of enqueue, and the parenthetical hints that delete_task is the wrong tool when the task must survive. There is no explicit 'use this when...' clause or statement of preconditions (e.g., task must currently be queued).

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