Skip to main content
Glama
m0xai

Trello MCP Server with Python

by m0xai

get_card

Retrieve specific Trello card details by providing the card ID to access information from Trello boards.

Instructions

Retrieves a specific card by its ID.

Args:
    card_id (str): The ID of the card to retrieve.

Returns:
    TrelloCard: The card object containing card details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
card_idYes

Implementation Reference

  • The primary MCP tool handler function for 'get_card'. It takes a card_id, calls the CardService to fetch the Trello card, handles errors, and returns the TrelloCard object.
    async def get_card(ctx: Context, card_id: str) -> TrelloCard:
        """Retrieves a specific card by its ID.
    
        Args:
            card_id (str): The ID of the card to retrieve.
    
        Returns:
            TrelloCard: The card object containing card details.
        """
        try:
            logger.info(f"Getting card with ID: {card_id}")
            result = await service.get_card(card_id)
            logger.info(f"Successfully retrieved card: {card_id}")
            return result
        except Exception as e:
            error_msg = f"Failed to get card: {str(e)}"
            logger.error(error_msg)
            await ctx.error(error_msg)
            raise
  • Registration of the 'get_card' tool with the MCP server using mcp.add_tool.
    mcp.add_tool(card.get_card)
  • Helper service method in CardService that makes the actual Trello API call to retrieve the card by ID and parses it into a TrelloCard model.
    async def get_card(self, card_id: str) -> TrelloCard:
        """Retrieves a specific card by its ID.
    
        Args:
            card_id (str): The ID of the card to retrieve.
    
        Returns:
            TrelloCard: The card object containing card details.
        """
        response = await self.client.GET(f"/cards/{card_id}")
        return TrelloCard(**response)
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states it 'retrieves' a card, implying a read-only operation, but doesn't disclose behavioral traits like authentication requirements, error handling (e.g., what happens if the ID is invalid), rate limits, or response format details beyond mentioning a 'TrelloCard' object.

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 appropriately sized and front-loaded: the first sentence states the core purpose, followed by structured Args and Returns sections. Every sentence earns its place with no wasted words, making it easy to scan.

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 low complexity (single parameter, no output schema, no annotations), the description is minimally adequate but lacks completeness. It covers the basic purpose and parameter but omits behavioral context (e.g., error cases, auth needs) and doesn't fully explain the return value beyond naming the object type.

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, the description compensates by explaining the single parameter's purpose ('The ID of the card to retrieve'), adding meaning beyond the schema's bare title. However, it doesn't specify format constraints (e.g., length, pattern) or examples, leaving some gaps.

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 card by its ID'), distinguishing it from sibling tools like get_cards (plural) which likely lists multiple cards. 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 when you need a single card identified by its ID, but it doesn't explicitly state when to use this vs. alternatives like get_cards or other retrieval tools. No guidance on prerequisites, exclusions, or comparative contexts is provided.

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