Who Tb

Multiple tools have heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all enable data lookup, while polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, and polymarket_kalshi_spread all target prediction-market analysis. An agent would struggle to pick the right one without reading very long descriptions.

Naming follows no consistent pattern. Some tools use verb_noun (list_subscriptions, resolve_entity, validate_claim), some use noun_phrase (polymarket_edges, resolution_audit), and some are verb+name with no separator (ask_pipeworx, forget, recall). The who_tb_* tools are consistent among themselves but clash with the rest of the set.

40 tools is on the heavy side for a single server, and the mismatch with the server name is extreme: 'Who Tb' suggests a focused tuberculosis toolkit, yet only 4 of 40 tools are TB-related. The bulk covers prediction markets, SEC data, and general research, making the server feel scattershot rather than purpose-built.

As a TBer-focused server, major gaps exist: no drug-resistance data, treatment outcomes, or newer TB indicators beyond budget/estimates/notifications/dictionary. As a general data platform, it covers many areas but still lacks obvious lifecycle operations (e.g., no update/delete for subscriptions beyond unsubscribe, no write path for most data). The domain is too diffuse to assess coherently.