Skip to main content
Glama

move_task

Destructive

Move a Kaiten card to another board, column, or lane, and set its sort order or previous-card position.

Instructions

Move a task via Kaiten card PATCH (board/column/lane/sort/prev_card_id).

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

Input Schema

NameRequiredDescriptionDefault
card_idYes
lane_idNo
board_idNo
column_idNo
sort_orderNo
prev_card_idNo

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
titleYes
changedYes
_metricsNo
locationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered structurally. The description adds only the implementation detail 'via Kaiten card PATCH' and does not explain what happens to unspecified placement fields (e.g., whether omitting lane_id clears or preserves the lane) or what a move disrupts.

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, correctly leading with the action. It is compact to the point of under-specification, but there is no wasted wording.

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

Completeness3/5

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

An output schema exists, so return values need not be described, and the annotations cover the mutation risk profile. However, for a destructive 6-parameter move operation with 0% schema coverage, the description omits the placement-semantics detail an agent needs to call it correctly.

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%, so the description carries the burden, yet it only repeats parameter names in parentheses without explaining their meaning or interaction. It does not clarify how sort_order and prev_card_id conflict, or whether board_id/column_id/lane_id must be supplied together, leaving 6 parameters materially 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?

States a specific verb and resource ('Move a task') and names the underlying mechanism (Kaiten card PATCH) plus the fields involved. It does not differentiate from the sibling 'update_task', which plausibly also changes board/column placement, so an agent cannot fully distinguish them from the text alone.

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 guidance on when to use this versus 'update_task' or how to choose between column_id, lane_id, sort_order, and prev_card_id. The parenthetical field list implies capability but gives no conditions or prerequisites for use.

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