Skip to main content
Glama
diegofornalha

MCP Server Trello

get_my_cards

Retrieve all Trello cards assigned to the current user, enabling efficient task management and organization within MCP Server Trello.

Instructions

Fetch all cards assigned to the current user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'get_my_cards': calls trelloClient.getMyCards() and returns JSON stringified response.
    case 'get_my_cards': {
      const cards = await this.trelloClient.getMyCards();
      return {
        content: [{ type: 'text', text: JSON.stringify(cards, null, 2) }],
      };
    }
  • src/index.ts:206-214 (registration)
    Registers the 'get_my_cards' tool in the MCP server with description and empty input schema.
    {
      name: 'get_my_cards',
      description: 'Fetch all cards assigned to the current user',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • TrelloClient method that implements the core logic: fetches current user's cards via Trello API endpoint '/members/me/cards'.
    async getMyCards(): Promise<TrelloCard[]> {
      return this.handleRequest(async () => {
        const response = await this.axiosInstance.get('/members/me/cards');
        return response.data;
      });
    }
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 of behavioral disclosure. While 'fetch' implies a read-only operation, it doesn't specify critical details like whether this requires authentication, how results are paginated or sorted, what happens if no cards are assigned, or potential rate limits. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 a single, clear sentence that front-loads the essential information ('fetch all cards assigned to the current user') with zero wasted words. It's appropriately sized for a simple, parameterless tool and efficiently communicates the core purpose without unnecessary elaboration.

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 (0 parameters, no output schema, no annotations), the description is minimally adequate. However, it lacks context about the return format (e.g., what data fields are included, if it's a list of objects) and behavioral traits like error handling or dependencies. For a read operation with no structured output documentation, more completeness would be helpful for an agent to use it effectively.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately adds no parameter details, as it's a parameterless tool. This earns a baseline 4, as the description doesn't need to compensate for any schema gaps.

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 ('fetch') and resource ('cards assigned to the current user'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_cards_by_list_id' or 'get_recent_activity', which also retrieve card-related data but with different scopes or filters.

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. For example, it doesn't clarify if this should be used instead of 'get_cards_by_list_id' when needing all user cards versus cards in a specific list, or how it relates to 'get_recent_activity' for recent updates. Without such context, the agent must infer usage from the tool name alone.

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

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

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