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

create_board

Create a new Kanban board with custom columns to organize tasks and workflows in Yokan Board MCP.

Instructions

Creates a new Kanban board with an optional list of initial column names.

Args: name (str): The name of the new board. auth (AuthContext): The authentication context containing user ID and token. columns (List[str], optional): A list of names for initial columns. Defaults to an empty list.

Returns: int: The ID of the newly created board.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
authYes
columnsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler implementation for the 'create_board' tool, registered using @app_instance.tool and @error_handler.
    async def create_board(
        name: str,
        auth: AuthContext,
        columns: List[str] = [],
    ) -> int:
        """Creates a new Kanban board with an optional list of initial column names.
    
        Args:
            name (str): The name of the new board.
            auth (AuthContext): The authentication context containing user ID and token.
            columns (List[str], optional): A list of names for initial columns. Defaults to an empty list.
    
        Returns:
            int: The ID of the newly created board.
        """
        data = (
            {
                "columns": {col: {"id": col, "title": col, "tasks": []} for col in columns},
                "columnOrder": columns,
            }
            if columns
            else {}
        )
        return await yokan_client.create_board(
            user_id=auth.user_id, name=name, data=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 the full burden. It states the tool creates a new board but doesn't disclose behavioral traits like whether this requires specific permissions, if it's idempotent, what happens on failure, or any rate limits. The mention of 'auth' parameter hints at authentication needs, but this isn't explicitly explained in the description text.

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. The first sentence states the purpose clearly, followed by a parameter list and return value. Every sentence adds value, though the parameter descriptions could be slightly more concise (e.g., 'auth' explanation is minimal but adequate).

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?

Given the tool's moderate complexity (creation operation with auth), no annotations, and an output schema that specifies the return type (int ID), the description is reasonably complete. It covers the core action and parameters, though it lacks behavioral context like error handling or side effects, which would be helpful for a mutation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 adds meaningful semantics for all three parameters: 'name' is for the board name, 'auth' is for authentication context, and 'columns' is for initial column names. This goes beyond the bare schema, though it doesn't detail format constraints (e.g., length limits for name).

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: 'Creates a new Kanban board with an optional list of initial column names.' It specifies the verb ('creates') and resource ('Kanban board'), distinguishing it from sibling tools like create_column or create_task. However, it doesn't explicitly differentiate from update_board or get_board beyond the action verb.

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., authentication requirements), when not to use it, or how it relates to sibling tools like create_column (which might be used after board creation) or update_board (for modifying existing boards).

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