Drug Prices

The set contains several overlapping general-purpose tools: ask_pipeworx, ask_pipeworx_beta (explicitly identical today), ask_pipeworx_grounded, deep_research, validate_claim, and discover_tools all function as broad research/query entry points. The prediction-market family also has a lot of overlapping surface between bet_research, polymarket_arbitrage, polymarket_edges, polymarket_fill_risk, and polymarket_kalshi_spread. The drug-price tools themselves are distinct, but the broader set has multiple ambiguous boundaries.

Most names are readable snake_case, and several follow a source-prefix convention like nadac_price, asp_payment_limit, and b340_covered_entities. However, there is a mix of verb-first names (ask_pipeworx, resolve_entity, validate_claim), noun-first tools (entity_profile, company_facts, release_calendar_markets), and bare verbs (remember, forget). It is not chaotic, but it lacks a single consistent naming pattern.

42 tools is beyond the 'too many' threshold for a server named Drug Prices, and most tools are unrelated to drug pricing—covering prediction markets, SEC data, npm packages, memory, company profiles, and nosedive market scans. The direct drug-price surface is only a handful of tools, so the set feels padded with generic Pipeworx/AI utilities. A focused server for this domain would likely need fewer than 15 tools.

The drug-pricing core covers useful ground: NADAC acquisition price, NADAC history, MEDICARE Part B ASP limits, 340B covered entities, contract pharmacies, and drug-vs-drug comparisons. It is missing several common pricing references such as WAC/AWP, Medicare Part D costs, or list price data, though ask_pipeworx may be able to reach some of those indirectly. This is not a dead end, but the advertised domain has notable gaps in its direct tool surface.