Vaers

Most tools have distinct purposes, but the ask_pipeworx family is a real ambiguity trap: ask_pipeworx_beta is explicitly documented as currently identical to ask_pipeworx, and ask_pipeworx_grounded only differs by extraction behavior. The five polymarket_* tools also require reading very long descriptions to keep straight, though their boundaries are genuinely different.

All names are clean lowercase snake_case and readable, but conventions are mixed: verb-first names (ask_, compare_, discover_, validate_, forget) sit alongside noun-first names (vaers_events_by_symptom, polymarket_arbitrage, company_facts, resolution_audit). The ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded trio is also a confusingly parallel naming pattern despite being distinct tools.

39 tools is far too many for a server named 'Vaers' — only 3 of them actually touch VAERS data. The rest span prediction markets, SEC filings, memory storage, npm dependency checks, AI visibility, subscriptions, and an everything-router, which makes the scope incoherent rather than merely large.

For the VAERS domain the server is named after, the surface is severely thin: only aggregate counts by vaccine and symptom, with explicit refusal to return individual report records, demographics, narratives, or time-series breakdowns. Outside that, the polyglot tool set covers its sub-domains unevenly — prediction markets are heavily covered while the nominal domain is a stub.