Skip to main content
Glama

move_task

DestructiveIdempotent

Change a task's status by moving it between workflow stages such as todo, in_progress, review, or done. Optionally reassign the task, add a comment before the move, and choose a lean or full result.

Instructions

Change task status (e.g. todo → in_progress → done). Status is given as a slug (not a UUID). On move to 'review', task auto-reassigns to creator unless assignee_id is provided. Returns {task, new_status} with a lean task by default (id, status_id, assignee, updated_at — the post-move assignee is always included so an auto-reassign is visible); full=true returns the whole reloaded task.

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>",
      "status_slug": "<status_slug>"
    },
    "name": "move_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
fullNoReturn the whole reloaded task instead of the lean confirmation.
commentNoOptional comment, written before the move so it lands even when the move hands the card (and its lock) to someone else.
task_idYesTask ID.
assignee_idNoReassign to this agent/user on move. Overrides auto-reassign to creator on review.
status_slugYesTarget status slug (e.g. 'in_progress', 'done').
assignee_typeNoAssignee type if assignee_id is set: user or agent.agent

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.8
    • changedInput schema / properties / comment / description
      Previous value: -"Optional comment to add when moving."New value: +"Optional comment, written before the move so it lands even when the move hands the card (and its lock) to someone else."
  2. First observedv0.1.1

TDQS

A3.8/5.0
Behavior4/5

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

With destructiveHint=true and idempotentHint=true already supplied, the description adds real context beyond annotations: the auto-reassign to creator on 'review' moves, why the comment is written pre-move (lock/card handoff), and exactly what the response contains. It stops short of explaining what the destructive flag means in practice — whether prior status history is overwritten or whether invalid transitions are rejected.

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?

One compact paragraph, front-loaded with the action and the slug convention, then the exception case, then the return shape. Every clause carries information — no filler and no repetition of the name.

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 six-parameter mutation tool with no output schema, the description covers the core action, the notable side effect, and the return payload in enough detail to call it confidently. The remaining gap is failure/transition semantics (invalid slug, disallowed backward transitions) which matter for a tool flagged destructive.

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%, so the schema already documents all six parameters including full, comment, assignee_id and assignee_type. The description reinforces the slug-not-UUID convention and the assignee_id override of auto-reassign, which is mild added value, but most of its parameter content restates what the schema already says.

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 opens with a specific verb+resource ('Change task status') and even illustrates the transition sequence (todo → in_progress → done). It is clearly a status-mutation tool, but it never names or contrasts with overlapping siblings such as finish_task, assign_task, or update_task, leaving the boundary to inference.

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 by the verb and the transition example, and the 'review' auto-reassign caveat tells the agent when to pass assignee_id. However, there is no explicit when-to-use/when-not guidance versus finish_task (which presumably also drives a card to done) or assign_task for the reassignment path — an agent with a 'close this card' intent has to guess.

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