Skip to main content
Glama
Sign In
Trello MCP Server

Trello MCP Server

by JulianKerignard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_trello_boards

List all Trello boards accessible to the authenticated user to identify and select a board for management.

Instructions

Liste tous les boards Trello accessibles à l'utilisateur authentifié

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_trello_boards"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It discloses a read-only listing operation and mentions authentication-dependent accessibility, which is useful. However, it does not mention response format, pagination, inclusion of closed boards, or error behavior, leaving some ambiguity for a tool with zero annotation support.

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, concise French sentence with no wasted words. The action ('liste') and scope are front-loaded, making it easy to parse quickly.

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

Completeness4/5

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

For a zero-parameter list tool with no output schema, the description is largely complete: it states what is returned (boards) and the scope (accessible to the authenticated user). It could mention whether closed boards are included or what fields are returned, but these are minor gaps given the tool's simplicity.

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 zero parameters and 100% coverage, so the baseline is 4. The description appropriately avoids inventing parameters and does not need to explain any parameter semantics.

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 uses a specific verb ('list') and resource ('Trello boards'), and adds the scope 'accessible to the authenticated user'. It clearly states the operation, though it does not explicitly contrast itself with sibling tools like list_trello_lists.

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 about when to use this tool versus alternatives such as search_trello_cards or list_trello_lists. There are no exclusions, prerequisites, or context that would help an agent choose among siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools