Skip to main content
Glama
TaylorChen

Multi-MCPs

by TaylorChen

get_board_cards

Retrieve all cards from a Trello board to view tasks and manage project workflows. Specify the board ID to access card details.

Instructions

Get cards on a Trello board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
board_idYes

Implementation Reference

  • Handler function that checks configuration, validates board_id argument, and calls the Trello client to retrieve board cards.
    async get_board_cards(args: Record<string, unknown>) {
      if (!cfg.trelloKey || !cfg.trelloToken) throw new Error("TRELLO_KEY/TRELLO_TOKEN are not configured");
      const boardId = String(args.board_id || "");
      if (!boardId) throw new Error("board_id is required");
      return client.getBoardCards(boardId);
    },
  • TrelloClient class method that performs the API request to fetch all cards on a specified board.
    getBoardCards(boardId: string) {
      return this.request(`/boards/${boardId}/cards`, { query: this.authQuery() });
    }
  • JSON schema defining the input for the tool: an object with required 'board_id' string property.
    inputSchema: {
      type: "object",
      properties: { board_id: { type: "string" } },
      required: ["board_id"],
    },
  • Tool definition object registered in the Trello module's ToolRegistration, including name, description, and input schema.
    {
      name: "get_board_cards",
      description: "Get cards on a Trello board",
      inputSchema: {
        type: "object",
        properties: { board_id: { type: "string" } },
        required: ["board_id"],
      },
    },
  • Invocation of registerTrello() in the central tools registration array, integrating Trello tools into the MCP server.
    registerTrello(),
Behavior1/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. It only states the action ('Get') without detailing traits like whether it's read-only, requires authentication, has rate limits, returns paginated results, or what the output format is. This leaves critical behavioral aspects unspecified.

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, efficient sentence with zero waste. It's appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration. Every word earns its place, making it highly concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (a read operation with 1 parameter), lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral traits, parameter details, or return values, leaving gaps that hinder an AI agent's ability to use the tool effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 1 parameter with 0% description coverage, and the tool description adds no meaning beyond the schema. It doesn't explain what 'board_id' is (e.g., a Trello board identifier, format, or how to obtain it). With low schema coverage, the description fails to compensate, leaving the parameter undocumented.

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

Purpose3/5

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

The description 'Get cards on a Trello board' clearly states the action (get) and resource (cards on a Trello board), but it's vague about scope (e.g., all cards, filtered cards) and doesn't distinguish from siblings like 'get_boards' or 'update_card'. It avoids tautology by specifying the resource beyond the tool name.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a board ID), exclusions, or how it differs from related tools like 'get_boards' or 'search_pages'. The description implies usage but offers no explicit context.

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/TaylorChen/muti-mcps'

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