Pennsylvania Code

Multiple tools overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route lookups/research through the same underlying catalog, with the beta currently identical to the stable version. The prediction-market cluster (polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, polymarket_fill_risk, bet_research, resolution_audit, resolution_diff, polymarket_kalshi_spread) also blurs boundaries—several can surface cross-venue spreads or arbitrage opportunities, and it is not obvious which to select first.

Most names use snake_case, but the pattern is inconsistent: bare verbs (remember, recall, forget), product-style names (ask_pipeworx, deep_research, pipeworx_trending), noun_noun compounds (entity_profile, company_facts, resolution_audit, release_calendar_markets), and verb_noun compounds (compare_entities, resolve_entity, validate_claim, scan_dependency) are all mixed. Family prefixes (ask_pipeworx_*, polymarket_*, pipeworx_*) help readability, but there is no uniform verb-construction rule.

37 tools is far too many for the server's stated name 'Pennsylvania Code', which maps to only a single statute-lookup tool. Even viewed as a general data/prediction-market platform, the count is oversized and includes tangential utilities (generate_llms_txt, scan_dependency, ai_visibility_check, memory and feedback tools) that do not cohere with the core data-lookup/arbitrage theme.

Relative to the 'Pennsylvania Code' purpose, the surface is severely incomplete—there is no search, table-of-contents, title navigation, or administrative code coverage, only one statute section tool. Viewed as a general research/prediction-market platform, it has rich coverage in some areas (Polymarket/Kalshi analysis, SEC/EDGAR lookups) but also obvious dead ends and unrelated features (memory, feedback, llms.txt generation) that leave the overall surface fragmented with no clear lifecycle.