Data Qatar

Multiple tools are near-duplicates: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded share the same router and response shape; bet_research, polymarket_edges, and polymarket_edge_tracker all target prediction-market edge; ai_visibility_check and scan_competitor_ai_presence overlap heavily. While descriptions are detailed, an agent would struggle to pick the right tool confidently.

Most tools follow a descriptive snake_case pattern (polymarket_arbitrage, entity_profile, validate_claim, search_datasets). Minor deviations exist: bare verbs (query, remember, recall, forget, subscribe, unsubscribe) mix with noun-first names (company_facts, bet_research), and polymarket_edges vs polymarket_edge_tracker are confusingly similar.

39 tools is far too many for a server named 'Data Qatar' — only 3 tools (search_datasets, dataset_info, query) actually relate to Qatar open data. The rest span Pipeworx data routing, prediction markets, memory, subscriptions, AI visibility, npm scanning, and llms.txt generation, making the server a bloated grab bag rather than a focused toolset.

The Qatar open-data workflow (search → metadata → query) is complete for read-only access, and memory/subscription tools have full lifecycle coverage. However, the overall surface has dead ends: tools return pipeworx:// citation URIs but no fetch/read tool is exposed, and the server's stated identity as a Qatar data server is underserved by only 3 domain-specific tools.