Skip to main content
Glama
m0xai

Trello MCP Server with Python

by m0xai
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

get_board

Retrieve a specific Trello board by its ID to access board details and manage tasks within the Trello MCP Server.

Instructions

Retrieves a specific board by its ID.

Args:
    board_id (str): The ID of the board to retrieve.

Returns:
    TrelloBoard: The board object containing board details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
board_idYes

Implementation Reference

  • server/tools/board.py:20-39 (handler)
    The MCP tool handler function 'get_board' that retrieves a Trello board by ID, calls the BoardService, logs activity, and handles errors.
    async def get_board(ctx: Context, board_id: str) -> TrelloBoard:
    """Retrieves a specific board by its ID.

    Args:
        board_id (str): The ID of the board to retrieve.

    Returns:
        TrelloBoard: The board object containing board details.
    """
    try:
        logger.info(f"Getting board with ID: {board_id}")
        result = await service.get_board(board_id)
        logger.info(f"Successfully retrieved board: {board_id}")
        return result
    except Exception as e:
        error_msg = f"Failed to get board: {str(e)}"
        logger.error(error_msg)
        await ctx.error(error_msg)
        raise
  • server/tools/tools.py:11-11 (registration)
    Registration of the 'get_board' tool in the MCP server via mcp.add_tool.
    mcp.add_tool(board.get_board)
  • server/services/board.py:19-30 (helper)
    Supporting BoardService.get_board method that makes the Trello API call to fetch the board data and parses it into a TrelloBoard model.
    async def get_board(self, board_id: str) -> TrelloBoard:
    """Retrieves a specific board by its ID.

    Args:
        board_id (str): The ID of the board to retrieve.

    Returns:
        TrelloBoard: The board object containing board details.
    """
    response = await self.client.GET(f"/boards/{board_id}")
    return TrelloBoard(**response)

Tool Definition Quality

A3.7/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action ('Retrieves') and return type ('TrelloBoard'), but lacks details on permissions, error handling, rate limits, or whether it's a read-only operation. While 'retrieves' implies non-destructive, explicit safety context would improve transparency.

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 defines the tool's core function, and the subsequent lines document input/output semantics without redundancy or fluff.

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 the tool's simplicity (single parameter, no output schema, no annotations), the description covers the basics adequately. However, for a retrieval tool with no annotations, it could benefit from mentioning read-only nature or error cases. The return type 'TrelloBoard' is documented but without schema details, leaving some ambiguity about response structure.

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 adds meaningful context beyond the input schema, which has 0% description coverage. It explains that 'board_id' is 'The ID of the board to retrieve', clarifying the parameter's purpose and relationship to the tool's function. For a single parameter tool, this provides adequate semantic understanding.

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 ('a specific board by its ID'), distinguishing it from sibling tools like 'get_boards' (plural retrieval) and 'get_board_labels' (different resource). The verb+resource combination is precise and unambiguous.

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 context through 'by its ID' and the parameter documentation, suggesting this tool is for fetching a single known board. However, it lacks explicit guidance on when to use this versus alternatives like 'get_boards' for listing multiple boards or 'get_card' for other resources, leaving some ambiguity in tool selection.

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/m0xai/trello-mcp-server'

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