Pjm

Most tools target distinct resources, but the ask_pipeworx family (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research) shares an almost identical routing purpose and differs only by mode, and the prediction-market tools (polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk) heavily overlap. The very long descriptions do a lot of disambiguation work, but an agent still has to read carefully to pick the right variant.

Names are uniformly snake_case and mostly follow a predictable verb_noun or noun_verb pattern (resolve_entity, compare_entities, entity_profile, pjm_load_forecast). A few are noun-only or oddly ordered (remember, recall, forget, pjm_feeds), but nothing mixes camelCase or conflicting conventions.

40 tools is heavy for a single server, though the breadth of domains (PJM energy, financials, prediction markets, memory, monitoring) partly justifies it. Redundancy within the ask_pipeworx and polymarket families means not every tool clearly earns its place, pushing this toward the over-scoped end.

The surface is broad and covers meta-routing, entity resolution, financials, prediction markets, memory, and subscriptions, with pjm_feeds acting as a discovery escape hatch for PJM datasets beyond the four dedicated tools. Minor gaps (e.g. day-ahead LMP and capacity tools, PyPI/Cargo dependency scans) exist but are workable via generic tools.