Vendor Signals

Several meta-routing tools overlap heavily (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, suggest_questions), making it easy to pick the wrong entry point. The polymarket family also has multiple related scanners and trackers with fuzzy boundaries. Descriptions try to differentiate, but the set still has many tools that appear to do nearly the same thing in different modes.

All names use snake_case, but the broader convention is mixed: some tools are verb-first (compare_entities, validate_claim, resolve_entity) while many are noun-first (entity_profile, company_facts, vendor_coverage, polymarket_edges). Prefix families help readability, but there is no consistent verb_noun pattern across the full set.

39 tools is heavy for a server named Vendor Signals, and the surface actually spans a general data platform, prediction markets, memory, subscriptions, and vendor monitoring. The count feels bloated and off-scope rather than tightly curated for the stated purpose.

For a broad data-platform reading, coverage is extensive across querying, entity resolution, financial facts, comparisons, subscriptions, and research. But for the stated vendor-signal focus there are notable gaps: no way to add or request a new tracked vendor feed, and subscriptions support SEC/Fred/Polymarket events but not vendor changelog events. Read coverage of tracked vendors is decent, but monitoring and lifecycle coverage are incomplete.