Skip to main content
Glama
yokan-board
by yokan-board

move_task

Move tasks between columns on a Yokan Kanban board to update workflow status and organize project progress.

Instructions

Moves a task from one column to another.

Args: board_id (int): The ID of the board containing the task. task_id (str): The ID of the task to move. new_column_id (str): The ID of the destination column. auth (AuthContext): The authentication context containing user ID and token.

Returns: None

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
board_idYes
task_idYes
new_column_idYes
authYes

Implementation Reference

  • The `move_task` function, decorated with `@app_instance.tool`, implements the logic to move a task from one column to another on a Kanban board. It validates inputs, removes the task from its original column, appends it to the new column, and updates the board via the YokanClient.
    async def move_task(
        board_id: int,
        task_id: str,
        new_column_id: str,
        auth: AuthContext,
    ) -> None:
        """Moves a task from one column to another.
    
        Args:
            board_id (int): The ID of the board containing the task.
            task_id (str): The ID of the task to move.
            new_column_id (str): The ID of the destination column.
            auth (AuthContext): The authentication context containing user ID and token.
    
        Returns:
            None
        """
        board = await yokan_client.get_board(board_id=board_id, token=auth.token)
        if "columns" not in board.data or new_column_id not in board.data["columns"]:
            raise McpError(error=ErrorData(code=NOT_FOUND, message="New column not found"))
    
        task_to_move = None
        for column in board.data["columns"].values():
            for i, task in enumerate(column.get("tasks", [])):
                if task.get("id") == task_id:
                    task_to_move = column["tasks"].pop(i)
                    break
            if task_to_move:
                break
    
        if not task_to_move:
            raise McpError(error=ErrorData(code=NOT_FOUND, message="Task not found"))
    
        board.data["columns"][new_column_id].setdefault("tasks", []).append(task_to_move)
    
        await yokan_client.update_board(
            board_id=board_id, name=board.name, data=board.data, token=auth.token
        )
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action ('moves') but lacks behavioral details: it doesn't specify permissions needed (beyond auth), whether the move is reversible, error conditions (e.g., invalid IDs), or side effects (e.g., task history updates). This is inadequate for a mutation tool with zero annotation coverage.

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 well-structured and appropriately sized: a clear purpose sentence followed by Args and Returns sections. Every sentence adds value, with no fluff. It could be slightly more front-loaded by integrating parameter hints into the purpose, but it's efficient overall.

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

Completeness2/5

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

Given the complexity (a mutation tool with 4 parameters), lack of annotations, and no output schema, the description is incomplete. It covers the basic action and parameters but misses critical context: error handling, return values (beyond 'None'), permissions, and how it differs from sibling tools. This leaves the agent under-informed.

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 0%, so the description must compensate. It lists all 4 parameters with brief explanations in the Args section, adding meaning beyond the bare schema (e.g., 'destination column' for new_column_id). However, it doesn't clarify parameter relationships (e.g., board_id must contain task_id) or constraints (e.g., ID formats), leaving gaps.

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 clearly states the tool's purpose: 'Moves a task from one column to another.' This specifies the verb ('moves') and resource ('task'), making it easy to understand. However, it doesn't explicitly differentiate from sibling tools like 'update_task' or 'reorder_columns', which might also involve task/column modifications.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., task/column existence), exclusions (e.g., invalid moves), or comparisons to sibling tools like 'update_task' (which might handle other task changes). The agent must infer usage from the purpose alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yokan-board/yokan-board-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server