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

create_column

Add a new column to a Yokan board to organize tasks and workflows. Specify the board ID and column name to create the column.

Instructions

Creates a new column in a specified board.

Args: board_id (int): The ID of the board to add the column to. name (str): The name of the new column. auth (AuthContext): The authentication context containing user ID and token.

Returns: yokan_models.Column: The newly created column object.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
board_idYes
nameYes
authYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
tasksNo
titleYes
minimizedNo
highlightColorNo

Implementation Reference

  • The handler implementation for the 'create_column' tool. It creates a new column object, updates the board's column order, and persists the changes.
    async def create_column(
        board_id: int,
        name: str,
        auth: AuthContext,
    ) -> yokan_models.Column:
        """Creates a new column in a specified board.
    
        Args:
            board_id (int): The ID of the board to add the column to.
            name (str): The name of the new column.
            auth (AuthContext): The authentication context containing user ID and token.
    
        Returns:
            yokan_models.Column: The newly created column object.
        """
        board = await yokan_client.get_board(board_id=board_id, token=auth.token)
        if "columns" not in board.data:
            board.data["columns"] = {}
        if "columnOrder" not in board.data:
            board.data["columnOrder"] = []
        new_column_id = str(uuid.uuid4())
        new_column = yokan_models.Column(
            id=new_column_id,
            title=name,
            tasks=[],
            highlightColor="#AF522B",
            minimized=False,
        )
        board.data["columns"][new_column_id] = new_column.dict()
        board.data["columnOrder"].append(new_column_id)
        await yokan_client.update_board(
            board_id=board_id, name=board.name, data=board.data, token=auth.token
        )
        return new_column
  • src/main.py:194-195 (registration)
    Registration of the 'create_column' tool using the FastMCP decorator.
    @app_instance.tool
    @error_handler
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a creation operation but doesn't mention permission requirements, rate limits, side effects, or what happens if the board doesn't exist. The authentication parameter hints at security needs, but the description doesn't explain authorization requirements or error conditions.

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 with clear sections (purpose, Args, Returns) and uses minimal sentences. The opening statement is front-loaded with the core functionality. However, the Args section could be more concise by integrating parameter explanations into the main description rather than as a separate block.

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?

Given that there's an output schema (yokan_models.Column), the description doesn't need to detail return values. However, for a creation tool with 3 parameters and no annotations, the description should provide more behavioral context about permissions, errors, and constraints. It covers the basics but leaves significant gaps for safe and effective use.

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?

The description includes an Args section that documents all three parameters with basic types, but schema description coverage is 0%, so the schema provides no additional documentation. The description adds value by naming and typing parameters, but doesn't explain constraints (e.g., name length limits, valid board_id ranges) or the AuthContext structure beyond what's in the schema definition.

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 verb ('creates') and resource ('new column in a specified board'), making the purpose immediately understandable. It distinguishes from siblings like create_board or create_task by specifying the resource type. However, it doesn't explicitly differentiate from update_column or reorder_columns in terms of when to use each.

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 (like needing an existing board), when not to use it, or how it differs from similar tools like update_column or reorder_columns. The agent must infer usage from context 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