Macau Stats

Several clusters have fuzzy boundaries: ask_pipeworx_beta is currently byte-equivalent to ask_pipeworx, macau_indicator overlaps the four specialized Macau wrappers (macau_gaming_revenue, macau_employment, macau_population, macau_tourism), and polymarket_edges, polymarket_arbitrage, and bet_research all target prediction-market opportunities. The very detailed descriptions help, but several tools are near-duplicates or cover the same data through different lenses.

Names are consistently snake_case with strong prefix families (macau_*, polymarket_*, ask_pipeworx_*, resolution_*), but conventions mix: verb_noun actions (compare_entities, resolve_entity) sit alongside noun-phrase resources (macau_gaming_revenue, entity_profile, company_facts) and bare-verb memory tools (remember, recall, forget). The pattern is readable but not uniform.

42 tools is well above the 25+ threshold and grossly oversized for a server named 'Macau Stats' — only 6 of the tools are Macau-specific. The remaining 36 cover a general-purpose data, prediction-market, memory, and subscription platform, which suggests the server is trying to be several products at once.

For its actual broad scope, the surface is fairly complete: discovery (discover_tools, suggest_questions), lookup (ask_pipeworx), grounded answers, deep research, entity resolution, comparison, verification, prediction-market analysis, and full memory/subscription lifecycles are all present. Minor gaps exist — resolution_audit references polymarket_market/kalshi_market and company_facts references get_company_financials, none of which are exposed as tools — but agents can work around them.