Datafiniti

Several tools occupy nearly identical roles: ask_pipeworx, ask_pipeworx_beta (explicitly identical today), ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all blur the line between routing, discovery, and answering. The prediction-market family (polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread) also heavily overlaps, making misselection likely without careful reading.

Names are uniformly lowercase snake_case, but there is no consistent verb_noun convention: some are verbs (remember, forget, validate_claim), some are noun phrases (company_facts, entity_profile, polymarket_arbitrage), and family prefixes vary (ask_pipeworx*, polymarket_*, datafiniti_*). The result is readable but mixed.

39 tools is well beyond a well-scoped set, and many are redundant (ask_pipeworx_beta), one-off utilities (generate_llms_txt, scan_dependency), or meta-tools that could be folded into fewer entry points. The count feels heavy for the server's apparent purpose.

The set covers a huge amount of research, entity, and prediction-market functionality, but it is a grab-bag rather than a coherent lifecycle, with notable gaps such as no direct market detail/quote tool and no Datafiniti record-level operations beyond search. Agents can often work around gaps via ask_pipeworx, but the surface is uneven.