No user-submitted related servers found.
Scored across 37 tools
Several tools occupy closely related domains: multiple mailbox-read variants (get_messages, get_messages_summary, peek_inbox_version), multiple task lifecycle tools, and multiple token-management tools. The descriptions do differentiate them, but the sheer overlap in purposes will still cause occasional mis-selection in an agent.
Tool names largely follow a verb_noun pattern (register_agent, send_message, post_task, get_channel_messages, delete_webhook), which is predictable and readable. The main inconsistency is task_schema_get, which inverts the standard get_* pattern seen elsewhere (get_task, get_tasks).
37 tools is an excessive surface for an MCP server, well beyond the 'too many' 25+ threshold even though the domain is broad. The count feels inflated by near-redundant read variants and several overlapping token/agent lifecycle tools that could be consolidated.
The tool surface covers nearly all important workflows for a bot relay: agent lifecycle, messaging, tasks, channels, webhooks, token management, and health. Minor gaps exist, such as no list_channels/delete_channel, no per-agent detail read, and no way to permanently delete messages, but agents can usually work around those.