Earthscope Fdsn

Several clusters of tools overlap heavily: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research all route natural-language questions; discover_tools / suggest_questions both surface what's available; entity_profile / company_facts / compare_entities / recent_changes all cover company data; and seven polymarket_* tools plus bet_research / resolution_audit / resolution_diff target prediction markets. The unusually detailed descriptions do explain when to pick which, which keeps this above a 2, but the boundaries still require careful reading.

Every name is snake_case with no camelCase or hyphen mixing, which is a strong baseline. Most follow a verb_noun pattern (ask_pipeworx, validate_claim, resolve_entity, scan_dependency, compare_entities), but a substantial minority are noun phrases (entity_profile, company_facts, release_calendar_markets, polymarket_edges, fdsn_events) so the convention is not fully uniform.

39 tools is well past the 16-25 'heavy' band and into the 25+ 'too many' range, and the server is named for a narrow seismic domain (Earthscope Fdsn) yet ships a general-purpose gateway covering finance, prediction markets, memory, subscriptions, and AI marketing. The count would be defensible for a deliberate multi-pack gateway, but it is not appropriate for the stated scope.

For the named FDSN/seismic domain the surface is thin — only fdsn_availability, fdsn_events, and fdsn_stations, with no waveform/dataselect fetch despite descriptions referencing dataselect URLs. Judged as a general Pipeworx gateway it is broad (query, research, discovery, memory, subscriptions, feedback) but has minor gaps such as no update path for memory entries or subscriptions beyond delete/deactivate.