Ofgem

Descriptions work hard to differentiate tools, but there is real overlap: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded are near-identical routers (beta by design behaves the same as stable), deep_research also answers routed questions, and suggest_questions / discover_tools / pipeworx_trending all cover 'what can I do'. The company tools (company_facts, entity_profile, compare_entities, recent_changes, resolve_entity) are similarly clustered, though their descriptions differentiate them adequately.

Nearly everything is lower_snake_case, which is consistent, but the convention is not a uniform verb_noun pattern — some are noun-first (company_facts, entity_profile, resolution_audit) and prefixes vary (ask_, polymarket_, ofgem_, pipeworx_, resolution_) rather than one predictable scheme. Still readable and clearly grouped.

39 tools is well past the heavy threshold and includes clear redundancy: three ask_pipeworx variants, six polymarket_* tools, and multiple overlapping meta/onboarding/discovery tools. For a server nominally scoped to Ofgem, only three tools are actually Ofgem-specific, so the count is disproportionate to the apparent purpose.

Coverage across its broad ambition is thorough — research/routing, company data, prediction-market analysis, identity resolution, memory (remember/recall/forget), subscriptions (subscribe/list/unsubscribe/recent_alerts), and meta-feedback are all present with sensible lifecycle coverage. Only minor gaps and the ofgem-vs-gateway scope mismatch keep it from a 5.