Crtsh

Descriptions work hard to disambiguate with explicit 'PREFER OVER' guidance, which helps a lot. But there is real overlap: ask_pipeworx, ask_pipeworx_beta (currently byte-identical), and ask_pipeworx_grounded do nearly the same routing, and entity_profile / company_facts / compare_entities / recent_changes / resolve_entity form a cluster an agent could easily mis-select. The crypto-market tools (polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, polymarket_fill_risk, bet_research) also blur together.

Predominantly consistent snake_case verb_or_noun patterns, with clear domain prefixes (crtsh_, polymarket_, pipeworx_, ask_pipeworx_). A few single-word outliers (remember, forget, recall, subscribe, unsubscribe, deep_research) deviate but remain readable and intuitive.

42 tools is well past the 25+ 'heavy' threshold and reflects an unbounded multi-domain gateway rather than a scoped server. The label 'Crtsh' implies certificate transparency but only 2 tools are crt.sh tools, so the surface vastly overreaches its apparent purpose.

Coverage is broad and largely closes lifecycle loops: memory has create/read/delete, subscriptions have create/list/cancel plus alert retrieval, and discovery/feedback/meta-tools exist. Minor gaps only (e.g. no subscription update, uneven coverage across the many heterogeneous packs), but nothing that obviously dead-ends an agent.