Skip to main content
Glama

move_task

Move a Kanboard task to another column by task ID and column name or ID, optionally placing it at the top or bottom of the destination column.

Instructions

Move a task to another column of its board (e.g. 'In progress', 'Done').

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

Input Schema

NameRequiredDescriptionDefault
columnYesColumn name (case-insensitive) or column ID
task_idYesKanboard task ID
positionNo1 = top; omit to put it at the bottom

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already indicate this is a non-read-only, non-destructive operation. The description adds useful scope by saying the target column belongs to the task's own board, but it does not state permission requirements, reversibility, or side effects beyond the schema-documented position behavior.

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?

The definition is a single front-loaded sentence with no unnecessary wording. The examples are compact and directly relevant to the column parameter.

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?

The tool has full parameter schema coverage, annotations that clarify safety, and an output schema, so return values need not be explained. The description is sufficient for calling the tool correctly, though it could be slightly more complete with guidance on sibling alternatives.

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%, so task_id, column, and position are already documented structurally. The description adds example column values like "In progress" and "Done," but does not add meaning beyond the schema for task_id or position.

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 states a specific verb and resource: "Move a task to another column of its board," including examples of target columns. It is clear what the tool does, but it does not explicitly distinguish itself from siblings such as update_task or close_task.

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 operation itself: use this when a task needs to change columns. However, there is no explicit when-to-use guidance, no exclusions, and no mention of when update_task or another sibling would be more appropriate.

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