Trengo MCP by usefulapi

Most tools target distinct resources and actions, and descriptions clearly separate ticket, contact, board, and metadata operations. The three reporting tools (aggregate metrics, agent performance, per-ticket details) overlap enough that an agent could occasionally misselect without reading carefully.

All tools follow the same trengo_ prefix and a consistent verb_noun snake_case pattern (e.g. create_ticket, list_contacts, update_board_card). The convention is predictable and readable throughout.

With 24 tools, the set is on the heavier side but reasonable for a broad helpdesk/omnichannel platform covering tickets, contacts, boards, reporting, and account metadata. Each tool appears to map to a distinct endpoint, so the count is largely justified.

Core ticket and contact lifecycles are partly covered, but there are notable gaps: no tool to list channels (required by create_contact/create_ticket), no ticket label management, no get/delete for contacts or tickets, and no board/stage listing despite board card tools. These gaps will force workarounds or cause failures for common workflows.