Launchdarkly

The set contains several near-duplicate clusters: ask_pipeworx vs ask_pipeworx_beta vs ask_pipeworx_grounded vs deep_research, the five polymarket_* trading tools, and remember/recall/forget. The descriptions are unusually explicit about routing and when to prefer which, which rescues many boundaries, but an agent still faces heavy overlap and version-variant tools that do almost the same thing.

Nearly everything is snake_case verb_noun (entity_profile, compare_entities, resolve_entity, subscribe, validate_claim), which is predictable. Minor deviations exist, such as the ld_ prefix on the four LaunchDarkly tools and noun-first meta names (pipeworx_feedback, polymarket_edges), but overall the conventions are readable and consistent.

45 tools is far beyond the typical well-scoped 3-15 range, and for a server named 'Launchdarkly' the count is wildly disproportionate to the four ld_* tools that actually match the name. The surface reads like an entire multi-domain data gateway, not a coherent LaunchDarkly toolset, so many tools feel like unrelated acquisitions rather than earned members of one set.

Judged against the stated domain (LaunchDarkly feature-flag management), the surface is severely incomplete: there is read access (ld_list_projects/environments/flags, ld_get_flag) but no create, update, toggle, or delete flag operations. The surrounding mass of finance/market/archive tools does not fill that gap, leaving the named domain with obvious dead ends for mutation workflows.