A Model Context Protocol (MCP) server for interacting with Trello boards
14 tools with consistent naming (verb_noun pattern) and basic schemas. Descriptions present but generic (avg ~60 chars, below 194-char baseline). All tools have input schemas with type definitions. Critical gaps: no output schemas documented, no error handling guidance, no parameter descriptions for most fields, missing idempotency/destructiveness hints. Tool 14 (search_board) has Spanish description mixed with English params, inconsistent. No tool annotations (readOnlyHint, destructiveHint). Schemas are minimal JSON Schema (type + description only); no constraints, enums, or ranges. Composition is sound (single responsibility per tool), but parameter design lacks depth.
Add a new card to a specified list
Add a new list to the board
Send a card to the archive
Send a list to the archive
Get a list of all available Trello boards
Fetch cards from a specific Trello list
Get information about the currently selected board
No output schemas documented. LLMs cannot plan downstream tool calls or extract required fields (e.g., card IDs for move_card). Every tool lacks a documented return type.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Agents cannot distinguish safe reads from destructive writes. archive_card, archive_list, update_card_details, add_card_to_list, move_card lack destructiveHint.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 53 | 2026-07-28+ | v2 |
Retrieve all lists from the specified board
Fetch all cards assigned to the current user
Fetch recent activity on the Trello board
Move a card to a different list, optionally to a different board
Buscar contenido específico dentro de un tablero de Trello
Switch to a different Trello board
Update an existing card's details
Descriptions too generic and short (avg ~60 chars vs 194-char baseline). Missing WHEN to use, prerequisites, and recovery guidance. E.g., 'Switch to a different Trello board' does not explain what happens to current context or when to call it.
search_board (tool 14) has Spanish description ('Buscar contenido específico...') mixed with English parameter descriptions. Inconsistent language breaks LLM parsing and user experience.
No error handling guidance. Tools lack recovery hints (e.g., 'If board not found, call get_available_boards first'). Agents cannot self-correct on failures.