Pulse Verity

Several clusters overlap: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research all answer research questions; polymarket_edges / polymarket_arbitrage / polymarket_edge_tracker / polymarket_fill_risk all concern prediction-market edges; company_facts / entity_profile / compare_entities / recent_changes all surface company information. The descriptions are unusually detailed and explicitly steer between tools, which prevents a lower score, but the boundaries still require careful reading.

All 42 names use snake_case with clear domain prefixes (pulse_, polymarket_, pipeworx_, ask_) and no camelCase or chaotic mixing. The pattern is mostly consistent, though many tools are noun phrases rather than verb_noun (e.g. entity_profile, company_facts, resolution_audit, pulse_key_ring).

42 tools is far beyond the typical 3–15 well-scoped range and spans many unrelated domains: signed crypto prices, prediction markets, general research, memory, subscriptions, AI visibility, llms.txt generation, and npm dependency checks. Even for a broad gateway server, this is over-heavy and dilutes the apparent purpose.

Coverage is broad and mostly complete across the domains present: Pulse Verity has catalog, key ring, single/batch signed prices, settlement print, and offline verification; prediction markets cover research, arbitrage, edges, fill risk, cross-venue spreads, and resolution auditing; memory and subscriptions have create/read/delete lifecycles. Minor gaps exist (e.g. no batch verification for signed prints, no update operation for memory), but agents can work around them.