Nci Evs

The core EVS tools (evs_search_concepts, evs_concept, evs_concept_relations, evs_terminologies) are clearly distinct, but the set is dominated by overlapping meta-tools: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research all route questions to the same catalog with only subtle mode differences, and the five polymarket_* tools plus bet_research have fuzzy boundaries (edges vs arbitrage vs edge_tracker vs fill_risk). The verbose descriptions explicitly state preference rules, which rescues the set from worse confusion, but an agent must read carefully to pick correctly.

All names are snake_case with no camelCase mixing, and pack families use consistent prefixes (evs_*, polymarket_*, ask_pipeworx*). There is a mild split between verb_noun forms (resolve_entity, validate_claim, scan_dependency, compare_entities) and bare noun phrases (company_facts, entity_profile, recent_alerts, release_calendar_markets), but the pattern is still predictable and readable.

40 tools is well above the heavy band, and the surface is far broader than the stated 'Nci Evs' scope — only 4 tools are EVS terminology lookups while the rest span finance, prediction markets, memory, research, and meta-routing. The count is defensible only as a general gateway, not for a vocabulary server, and the ask_pipeworx variants pad the set with near-duplicates.

For the EVS domain the surface covers the main lifecycle: search to find a C-code, fetch the full concept record, traverse parents/children/roles, and enumerate served terminologies with versions. Minor gaps remain (no subset listing, no multi-hop path/parent-tree expansion, no SPARQL/suggest endpoint), but agents can work around them via evs_concept_relations.