No user-submitted related servers found.
Scored across 36 tools
Most tools target distinct resources and the descriptions carefully differentiate them (e.g. splithub_status vs splithub_experiment_status vs splithub_results), but there are several overlap traps: four deprecated alias tools (splithub_create_experiment, splithub_set_status, splithub_create_property, splithub_set_property_status) duplicate existing tools with reversed-word names, splithub_remove overlaps splithub_ship, and splithub_property_create overlaps splithub_analytics_connect. An agent can disambiguate with careful reading, but the aliases and near-duplicates are real misselection risk.
There is a consistent splithub_ prefix and mostly snake_case, but the convention is mixed: bare-noun tools (status, results, plan, ship, refs, domains, links, notes, alerts) sit alongside noun_noun tools (experiment_create, analytics_funnel), and verb placement is inconsistent — splithub_property_create and splithub_create_property both exist, one deprecated. Multi-action tools (links, notes, alerts, analytics) pack CRUD into an action parameter, further diverging from the verb_noun pattern.
36 tools is above the 25+ threshold and feels heavy, especially since 4 of them are deprecated one-release aliases that should not inflate the surface. The domain is genuinely broad (experiments plus a full analytics suite), but the set could be consolidated (e.g. links/notes/alerts/se gems action multiplexing is already used elsewhere).
Coverage is exceptional: full experiment lifecycle (plan → create → doctor/refs → push → results → status → ship/remove → review), full analytics suite (properties, funnel, paths, retention, realtime, events, segments), plus links, alerts, notes, domains, and cloud connection/init tooling. Obvious dead ends are rare — remaining gaps (alert channel config, link targeting) are explicitly dashboard-only and documented.