Skip to main content
Glama

move_task

Idempotent

Moves a task to another kanban board or column within its project, optionally placing it at the top or bottom of the target column.

Instructions

Move a task to another kanban board (column) of its project.

board: board title or id (within the task's project). position: "top" or "bottom" of the target column.

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

Input Schema

NameRequiredDescriptionDefault
boardYes
task_idYes
positionNobottom

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare non-readonly, idempotent, non-destructive, open-world behavior, covering the safety profile. The description adds useful scoping ('within the task's project') but says nothing about failure modes such as a nonexistent board, an invalid position value, or moving a task already in the target column.

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?

Two short sentences plus a compact two-line glossary for the non-obvious parameters; the action is front-loaded with zero filler. The parenthetical '(column)' earns its place by clarifying an ambiguous term.

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?

An output schema exists so return values need no explanation, and for a 3-parameter tool the description covers the two non-obvious parameters adequately. Only edge-case behavior (invalid board, no-op moves) is absent.

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 0%, so the description must carry parameter meaning. It defines 'board' (title or id, scoped to the task's project) and 'position' (top/bottom), which is genuinely additive, but task_id is unexplained and the allowed values for position/default of 'bottom' are already in the schema, leaving the compensation partial.

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 to another kanban board') and disambiguates 'board' as a column within the task's project. It does not explicitly contrast with update_task, which might also alter board placement, so sibling differentiation is implied rather than stated.

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?

The description implies usage (repositioning a task between columns) but gives no explicit when-to-use or when-not-to-use guidance relative to update_task or set_task_progress. No prerequisites or preconditions are mentioned.

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