New Jersey Code

Several clusters overlap heavily: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research all route questions to the same 6,897-tool catalog (beta is even documented as currently identical to stable), and the Polymarket suite (polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread, bet_research) plus the company-research suite (entity_profile, company_facts, compare_entities, resolve_entity, recent_changes) require careful reading to separate. Descriptions do draw real boundaries in most cases, but the volume of near-duplicates makes misselection likely.

Everything is snake_case, which is consistent, and namespacing (polymarket_*, pipeworx_*, nj_*) is predictable. The only deviation is verb-phrase vs noun-phrase mixing (resolve_entity / validate_claim vs company_facts / entity_profile / bet_research), which is minor and still readable.

43 tools is well above the comfortable 3-15 range and heavy even for a gateway. The count is inflated by near-duplicate variants (three ask_pipeworx routers) and by bundling unrelated domains (NJ statutes, SEC, Polymarket, archiving, memory, subscriptions) into one surface.

Some areas are genuinely complete — memory (remember/recall/forget) and subscriptions (subscribe/unsubscribe/list_subscriptions/recent_alerts) form full lifecycles, and the Polymarket tooling is deep. However the server is named 'New Jersey Code' yet carries only two NJ-specific tools (nj_statute_search, nj_statute_section) with no browse/index or case-law surface, so coverage relative to the stated domain is thin and the overall scope is muddled.