Carsxe

Most carsxe_* and Polymarket tools are clearly distinct, but the three ask_pipeworx variants plus deep_research create overlapping entry points, and entity_profile/company_facts/compare_entities all touch company fundamentals. The lengthy descriptions resolve most ambiguity, but misselection is still possible without careful reading.

Names are mostly snake_case but follow no consistent verb_noun pattern: ask_pipeworx, entity_profile, company_facts, recent_changes, resolution_audit, and generate_llms_txt mix verbs, nouns, and adjective-noun phrases. Prefixes like ask_, scan_, and polymarket_ provide some structure, but conventions clash across the set.

At 40 tools, the surface is overloaded and spans at least four distinct domains: Carsxe vehicle lookups, Pipeworx data routing, prediction-market analytics, and memory/subscription meta-tools. The breadth could justify a large platform, but as exposed here it feels like several servers merged into one.

The Pipeworx side is broad: lookup, grounded verification, deep research, entity resolution, comparison, validation, discovery, alerts, and memory are covered. However, the Carsxe-specific slice is only four read-only tools with no search-by-make/model or batch capability, and ask_pipeworx_beta is a redundant duplicate rather than a distinct capability.