Skip to main content
Glama
TaylorChen

Multi-MCPs

by TaylorChen

get_boards

Retrieve Trello boards for authenticated users to manage project organization and track tasks across multiple integrated services.

Instructions

Get Trello boards for the authenticated user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that implements the core logic of the 'get_boards' tool, checking for Trello credentials and calling the client's getBoards method.
    async get_boards() {
      if (!cfg.trelloKey || !cfg.trelloToken) throw new Error("TRELLO_KEY/TRELLO_TOKEN are not configured");
      return client.getBoards();
    },
  • The tool registration object defining the name, description, and input schema for 'get_boards' within the Trello API registration.
    {
      name: "get_boards",
      description: "Get Trello boards for the authenticated user",
      inputSchema: { type: "object", properties: {} },
    },
  • Helper method in TrelloClient that performs the actual API request to retrieve the user's boards.
    getBoards() {
      return this.request(`/members/me/boards`, { query: this.authQuery() });
    }
  • Top-level registration where registerTrello() is called to include the Trello tools (including get_boards) in the MCP server.
    registerTrello(),
  • Input schema for the get_boards tool, specifying an empty object (no input parameters required).
    inputSchema: { type: "object", properties: {} },
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. It mentions 'authenticated user,' hinting at auth needs, but doesn't disclose other behavioral traits such as rate limits, pagination, return format, or whether it lists all boards or filtered ones. 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, efficient sentence that directly states the tool's purpose without any fluff. It is appropriately sized and front-loaded, making it easy to understand at a glance. Every word earns its place.

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 has 0 parameters, no annotations, and no output schema, the description is minimally complete. It covers the basic purpose but lacks details on behavior, output, or usage context. For a simple list tool, this might be adequate, but it doesn't fully compensate for the missing structured data, leaving room for improvement.

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 tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter details, and it appropriately doesn't mention any. Baseline for 0 parameters is 4, as it avoids unnecessary information.

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 verb ('Get') and resource ('Trello boards'), specifying they are for the authenticated user. It distinguishes from siblings like get_board_cards (which gets cards within a board) and get_repository_info (different domain). However, it doesn't explicitly differentiate from all siblings, such as search_pages or list_commits, which are also list operations in other contexts.

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. It doesn't mention prerequisites (e.g., authentication requirements), exclusions, or comparisons to other tools like search_pages or list_commits. The context is implied (Trello boards for the user) but lacks explicit usage instructions.

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