Related Servers

Descriptions work hard to draw boundaries (card_archive vs card_delete, card_move vs card_position_set, card_label_add vs card_label_create_and_add, and the four *_actions tools scoped by resource). However, real overlaps remain: card_update explicitly covers due dates and archive state that card_due_date_set and card_archive also handle, and card_checklist_item_update claims completion state, checklist, and position — all owned by card_checklist_item_set_checked and card_checklist_item_move.

The dominant pattern is <resource>_<action> (board_get, card_create, label_delete), which is readable and mostly followed. But the `list_` prefix is overloaded: list_boards/list_workspaces mean 'enumerate', while list_get/list_update/list_archive mean 'the list resource' — and card_list vs list_cards are near-identical names with opposite meanings. That collision is a genuine trap for an agent.

77 tools is far beyond a reasonable surface and the granularity is excessive: board_get vs board_field_get, card_list vs card_board vs card_get, and separate tools for due date, position, cover, and archive on a card. While Trello is a large domain, many tools could be folded into a single card_update or board_get variant.

Coverage is broad and deep: full card lifecycle (create/update/move/archive/delete), checklists, labels, attachments, custom field values, members, workspaces, actions, and search. Gaps remain — no board update/archive/delete, no custom field definition create/update/delete (only get/options), and no board member add/remove, so board-level mutation is a dead end.