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

get_boards

Retrieve all Kanban boards for authenticated users to manage projects and workflows through the Yokan Board MCP server.

Instructions

Retrieves all Kanban boards for the authenticated user.

Args: auth (AuthContext): The authentication context containing user ID and token.

Returns: List[yokan_models.Board]: A list of Kanban boards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
authYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function `get_boards` implements the MCP tool, decorated with `@app_instance.tool` and `@error_handler`. It calls `yokan_client.list_boards` to fetch the boards.
    @app_instance.tool
    @error_handler
    async def get_boards(
        auth: AuthContext,
    ) -> List[yokan_models.Board]:
        """Retrieves all Kanban boards for the authenticated user.
    
        Args:
            auth (AuthContext): The authentication context containing user ID and token.
    
        Returns:
            List[yokan_models.Board]: A list of Kanban boards.
        """
        return await yokan_client.list_boards(user_id=auth.user_id, token=auth.token)
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it's a retrieval operation. It doesn't disclose behavioral traits like pagination, rate limits, error conditions, sorting, or whether it includes archived boards. The authentication requirement is mentioned but not elaborated.

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 appropriately sized with clear sections (purpose, args, returns). The first sentence efficiently states the core functionality. The args/returns sections are helpful but could be more integrated. No wasted sentences.

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?

For a simple retrieval tool with 1 parameter and an output schema (List[yokan_models.Board]), the description covers basic purpose and authentication. However, with no annotations and behavioral gaps (pagination, filtering, error handling), it's minimally adequate but lacks completeness for reliable agent use.

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?

With 0% schema description coverage and only 1 parameter, the description adds meaningful context by explaining that auth contains 'user ID and token' for authentication, which clarifies the parameter's purpose beyond the schema's structural definition. However, it doesn't detail how these fields are used.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Retrieves') and resource ('all Kanban boards for the authenticated user'), distinguishing it from siblings like get_board (singular) and create/update/delete operations. It precisely defines scope and ownership.

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?

The description implies usage for retrieving all boards for the current user, but doesn't explicitly state when to use this versus alternatives like get_board (for a specific board) or how it differs from other list operations. No explicit exclusions or prerequisites beyond authentication are mentioned.

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