crypto

Several clusters overlap heavily: ask_pipeworx/ask_pipeworx_beta/ask_pipeworx_grounded/deep_research all route a question to sources, and the beta tool is explicitly admitted to be identical to ask_pipeworx; entity_profile/compare_entities/recent_changes/resolve_entity all cover company research; six polymarket_* tools plus bet_research overlap on betting analysis; discover_tools/suggest_questions/pipeworx_trending all serve discovery. Descriptions give strong routing guidance, which rescues the set, but an agent still faces real misselection risk.

All names are lowercase snake_case with no casing-style mixing. Verb patterns vary (get_crypto_global vs get_crypto_price, entity_profile, polymarket_edge_tracker, recent_changes, ai_visibility_check), so there isn't one strict verb_noun template, but the convention is consistent and readable.

36 tools is heavy and the server name ('crypto') dramatically understates the true surface, which spans a universal data gateway, prediction markets, memory, subscriptions, and AI-marketing audits. Much of it is justified by that breadth, but redundant variants (ask_pipeworx_beta, discovery tools) push it above a well-scoped count.

Coverage is unusually rich: discovery, routing, grounded answers, entity resolution, company/drug comparison, crypto prices/history/market, prediction-market analysis, memory (remember/recall/forget), and subscription lifecycle (subscribe/list/unsubscribe/recent_alerts). Only minor gaps (e.g., no explicit update path for stored memory beyond forget-and-rewrite) keep it from a 5.