Ioos Erddap

Several tight clusters of near-duplicate tools exist: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research / discover_tools / suggest_questions / validate_claim all answer 'look up a fact from data', and polymarket_edges / polymarket_arbitrage / polymarket_edge_tracker / polymarket_fill_risk / polymarket_kalshi_spread / bet_research all target prediction-market edges. The very verbose descriptions do try to steer selection ('prefer X over Y'), but the boundaries are still fuzzy enough that misselection is likely.

Nearly everything is snake_case with a clear verb_noun or noun_noun shape, and prefixed families (ioos_erddap_*, polymarket_*, pipeworx_*, ask_pipeworx_*) group logically. Minor deviations (entity_profile, company_facts, release_calendar_markets, pipeworx_trending) are noun phrases rather than actions, but the convention is otherwise predictable.

44 tools is far past the well-scoped 3-15 range, and the inventory is an extreme mismatch for a server named 'Ioos Erddap' — only 5 of 44 tools touch IOOS/ERDDAP ocean data, while the rest are SEC, prediction-market, memory, and meta-router tools. The count and mix suggest a whole gateway catalog rather than a focused server.

For the apparent ERDDAP domain the surface covers search, dataset metadata, tabledap and a single-point griddap read, but lacks fuller gridded subset/region querying and dataset listing, so there are notable gaps. Judged as a general gateway the coverage is broad, but that breadth does not match the stated server purpose.