Xposedornot

Several tool clusters have unclear boundaries: email_breaches vs email_breach_analytics are near-duplicates, ask_pipeworx_beta is explicitly identical to ask_pipeworx, and the polymarket_* suite (edges, arbitrage, edge_tracker, fill_risk, kalshi_spread) overlaps heavily in purpose. Entity research tools also blur together (entity_profile, company_facts, compare_entities, recent_changes, resolve_entity), so an agent could easily pick the wrong tool despite long descriptions.

Names are uniformly snake_case but mix conventions: some are verb_noun (ask_pipeworx, compare_entities, resolve_entity, validate_claim) while many are noun_first or domain-prefixed (company_facts, email_breaches, entity_profile, polymarket_edges, recent_changes). The ask_pipeworx_beta variant also breaks the pattern with a version suffix, making the set readable but not fully predictable.

At 38 tools, this significantly exceeds the 3-15 well-scoped range and crosses the 'too many (25+)' threshold. While the server covers many domains, the count feels bloated because several tools are redundant variants or overlapping edge-detection utilities that could be consolidated.

For the server's apparent breadth, coverage is strong: it includes query routing (ask_pipeworx family), company research (profile/facts/compare/resolve), prediction-market analysis (arbitrage, edges, resolution, fill risk), memory lifecycle (remember/recall/forget), subscription lifecycle (subscribe/unsubscribe/list/alerts), and meta-discovery (discover_tools, suggest_questions). Minor gaps exist (e.g., no direct tool to edit an email breach report or update a remembered value), but no major dead ends are obvious.