Skip to main content
Glama
Sign In
Task Queue MCP

Task Queue MCP

by devops-riku
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Move a task

move_task

Moves a task to a named board column to start, resume, block, complete, or return work, or file it into another project.

Instructions

Moves a task to a board column by name, as dragging it on the board does: In Queue, In Progress (starts or resumes it), Blocked (needs reason), Done (completes it; reason is the completion note), or one of its project board’s own columns. It also moves back a step: from In Progress, Blocked or a later column to In Queue (back in the assignee’s queue, not started; the time worked so far stays), or to the pool (needs reason, and Return any task for work in progress). An unknown column lists the board’s columns. With folder, files it in another project (needs Manage projects). Reopening is done in Task 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": "<task>"
    },
    "name": "move_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesThe task: its number, e.g. TASK-000123, or its id.
columnNo
folderNoA project, or a path like "Website / Checkout".
reasonNoWhy: for Blocked and handing back. With Done, the completion note.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the basic safety annotations, the description details complex behavioral traits like state transitions, such as 'time worked so far stays' when moving back to In Queue. It also handles edge cases like unknown columns and provides context on where reopening is handled.

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?

The description is dense, but its complexity necessitates this length. It front-loads the primary action and then uses structured clauses to define all operational branches and constraints.

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

Completeness5/5

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

Given the high complexity and the various states and dependencies involved (e.g., managing time worked, handling unknown columns, and external project management), the description is highly complete for accurate invocation.

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?

The description clarifies the semantic ambiguity of the 'reason' parameter, stating it is used for 'Blocked', 'Done' (completion note), or 'handing back'. It also provides context for the 'folder' parameter, linking it to moving tasks between projects.

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?

The purpose is clearly defined as moving a task, but it goes further by detailing exactly how different column transitions map to specific actions like starting, resuming, or completing the task. It also identifies movement by folder/project.

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?

The tool provides exhaustive usage guidelines by covering not just standard forward movement, but also complex backward movement (to In Queue or Pool) and state dependencies (e.g., the reason parameter needed for Blocked or Done). It also outlines limitations, such as requiring 'Manage projects' for folder changes.

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

Deploy Server

Other Tools