Related Servers

While many tools are highly specialized, there is significant overlap across domains: set_site vs scaffold_site vs apply_site_template vs add_page vs edit_site_section all mutate site content, add_feature vs add_features_bulk vs plan_work vs import_tasks vs validate_feedback all create tickets, and list_tasks/get_task/get_board overlap in board views. Tools like get_metrics/export_metrics/export_tasks also have overlapping read purposes, forcing agents to carefully parse descriptions to choose correctly.

The dominant pattern is verb_noun (add_feature, list_media, set_status, get_kb_doc, remove_contact), but there are notable deviations: noun-first names (customer_portal, leads_map, routing_scorecard, license_status, bug_impact_scan), missing verbs (coverage_by_product, test_runs_by_suite), and abbreviation mixing (get_rag_explorer vs get_kb_doc, eval_report vs get_metrics). Most names are readable, but the inconsistent ordering and verb styles create a mixed convention.

217 tools is extreme for any single MCP server. The server appears to be a monolithic all-in-one business toolkit (board, CRM, media, website, email, campaigns, licensing, git, analytics, testing, RAG, packaging), each of which could be its own server. Even with a wide scope, no agent can efficiently discover or select from 217 tools, and the context cost alone makes the set unwieldy.

Within each subdomain the coverage is quite thorough: tickets have create/read/update/delete/status/sprint/attachment/comments, the CRM has companies/contacts/leads/bookings/agreements, the website has page/section/SEO/template/asset/analytics operations, and testing has generate/save/list/run/coverage flows. Minor gaps exist (e.g., no update_media/replace_media for assets, no campaign deletion, no direct email send), but the surface is generally deep enough to avoid dead ends.