Einpresswire

The descriptions work hard to disambiguate, but genuine overlap remains: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded share the same router and differ only in grounding/beta status, and the five polymarket_* tools (arbitrage, edges, edge_tracker, fill_risk, kalshi_spread) blur together despite long caveats. ai_visibility_check vs scan_competitor_ai_presence and entity_profile vs company_facts vs recent_changes also require careful reading to separate.

Names are consistently snake_case and mostly follow a verb_noun or domain_prefix pattern (einpresswire_*, polymarket_*, ask_pipeworx_*). Minor deviations exist — bare verbs (remember, recall, forget, subscribe) and noun-only names (company_facts, entity_profile, recent_changes) mixed with verb-first names — but the scheme stays readable and predictable.

39 tools is well above the 25+ threshold and includes redundant families (three ask_pipeworx variants, five polymarket tools, two AI-visibility scanners) that inflate the surface. The breadth spans unrelated domains (Pipeworx router, EIN Presswire, Polymarket trading, AI-marketing audits), so the set reads as several servers bundled into one rather than a tightly scoped toolset.

Coverage is broad and largely closed-loop: memory (remember/recall/forget), subscriptions (subscribe/unsubscribe/list/recent_alerts), EIN Presswire read path, and a deep Polymarket/Kalshi analysis suite. Gaps are minor — no subscription update, no write path for press releases, and resource-read is only referenced rather than exposed as a tool.