Skip to main content
Glama
yokan-board

Yokan Board MCP

Official
by yokan-board
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_columns

Retrieve all columns from a specified board in Yokan Kanban Board to organize and manage workflow tasks effectively.

Instructions

Retrieves all columns for a given board.

Args: board_id (int): The ID of the board to retrieve columns from. auth (AuthContext): The authentication context containing user ID and token.

Returns: List[yokan_models.Column]: A list of column objects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
board_idYes
authYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • src/main.py:234-251 (handler)
    The 'get_columns' handler function retrieves columns for a specified board from the Yokan client and returns them as a list of Column objects.
    async def get_columns(
    board_id: int,
    auth: AuthContext,
) -> List[yokan_models.Column]:
    """Retrieves all columns for a given board.

    Args:
        board_id (int): The ID of the board to retrieve columns from.
        auth (AuthContext): The authentication context containing user ID and token.

    Returns:
        List[yokan_models.Column]: A list of column objects.
    """
    board = await yokan_client.get_board(board_id=board_id, token=auth.token)
    if "columns" not in board.data:
        return []
    return [yokan_models.Column(**col) for col in board.data["columns"].values()]

Tool Definition Quality

B3.3/5.0
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 it's a retrieval operation but doesn't mention authentication requirements (implied by the auth parameter), potential rate limits, error conditions, or whether it returns all columns or is paginated. The description is minimal beyond stating the basic function.

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 description is efficiently structured with a clear purpose statement followed by well-organized Args and Returns sections. Every sentence adds value: the first states the action, and the subsequent lines document inputs and outputs without redundancy.

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 (2 parameters, no annotations, but with an output schema), the description is reasonably complete. It covers the purpose, parameters, and return type. The output schema handles return values, so the description doesn't need to detail them. However, it lacks behavioral context like error handling or usage constraints.

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?

The description explicitly documents both parameters (board_id and auth) with their types and purposes, adding meaningful context beyond the schema's structural definition. Since schema description coverage is 0%, this parameter documentation is essential and well-handled, though it could elaborate on auth requirements (e.g., valid token needed).

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 action ('Retrieves') and resource ('all columns for a given board'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_board' or 'get_tasks', which also retrieve data but for different resources.

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., needing a valid board_id), nor does it contrast with other retrieval tools like 'get_board' or 'get_tasks' that might be more appropriate in certain contexts.

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