Indiana Code

The set spans at least six unrelated domains (Indiana state law, AI visibility marketing, prediction-market arbitrage, entity/financial research, agent memory, Pipeworx meta-operations), and several tools overlap heavily: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded, and polymarket_edges / polymarket_arbitrage / polymarket_fill_risk all require careful reading to separate. Descriptions do disambiguate each pair, but the beta twin especially is a coin-flip for an agent.

Predominantly consistent verbose snake_case verb_noun, and prefixes (polymarket_, archive_, pipeworx_, ask_pipeworx_, in_code_) give useful namespace grouping. Deviations are minor: ask_pipeworx_beta / ask_pipeworx_grounded drop the namespace-style suffix, and polymarket_edge_tracker vs polymarket_edges differ by a near-invisible suffix.

42 tools is well past the point where a single server's surface is legible, especially since they serve many unrelated product areas. Real consolidation is available: three ask_pipeworx variants, three+ bet_research/polymarket_* scanners, and infra tools (remember/recall/forget, subscribe/list_subscriptions/unsubscribe) that could be pruned or merged.

Coverage within each declared domain is genuinely deep — entity resolution, financials, change feeds, side-by-side comparison, and fact-checking form a complete research loop, and the Polymarket/Kalshi area covers discovery, edge, decay, depth, and settlement audit. Gaps are minor (no explicit delete/update for stored memory beyond forget, no direct SEC filing-body fetch called out), and nothing critical is obviously missing.