Helius

Most tools are clearly distinct, but the ask_pipeworx/ask_pipeworx_beta/ask_pipeworx_grounded trio is intentionally redundant and could easily misfire without careful description reading. The five polymarket_* tools and the query/verification cluster (deep_research, validate_claim, company_facts) also have overlapping boundaries, though detailed descriptions mitigate misselection.

Snake_case is used uniformly and most names follow a readable noun_verb or verb_noun shape. However, the convention is mixed—entity_profile, company_facts, and polymarket_arbitrage are noun-first while ask_pipeworx, compare_entities, and validate_claim are verb-first—so the pattern is predictable but not perfectly consistent.

39 tools is well above the 25+ threshold and feels heavy even for a multi-purpose server. The breadth is justified by the overlapping domains (data querying, prediction markets, subscriptions, memory, Solana, AI visibility), but several tools could be consolidated or are near-duplicates, making the surface larger than necessary.

The core domains are well covered: subscription lifecycle is complete, memory is complete, prediction-market analysis includes edge detection, fill risk, and resolution auditing, and data querying has multiple complementary entry points. Minor gaps exist—no order placement for prediction markets and sparse Solana coverage (read-only, no balance/transaction-sending)—but these are arguably out of scope.