Arcgis Tempe

Many tools have clearly distinct purposes (memory triad, subscriptions, ArcGIS layer operations, Polymarket trading risk), but several high-level research/query entry points overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, bet_research, discover_tools, suggest_questions, and entity_profile all route or answer questions. The descriptions attempt to clarify when to use each, but ask_pipeworx_beta currently mirrors ask_pipeworx exactly and discover_tools/suggest_questions both serve discovery, so misselection remains likely.

Names are mostly snake_case and readable, but conventions are mixed: some are verb_noun (list_subscriptions, validate_claim), some noun_noun (polymarket_edges, layer_info), some verb-only (remember, recall, forget), and duplication markers vary (ask_pipeworx_beta vs ask_pipeworx_grounded; polymarket_edges vs polymarket_edge_tracker). There is no single predictable pattern across all 34 tools.

34 tools is heavy for a server named Arcgis Tempe, which implies a focused geospatial dataset surface; only three tools (search_datasets, query_layer, layer_info) directly serve Tempe GIS. The rest are a broad Pipeworx data gateway, Polymarket suite, memory, subscription, and AI-visibility set, making the package feel over-scoped and difficult to navigate as one server.

The Pipeworx-side surface is broad: question routing, grounded answers, deep research, entity resolution/profiling, comparisons, claim validation, subscriptions, memory, and extensive Polymarket tooling. For the ArcGIS Tempe side, however, coverage is thin—only search, schema inspection, and query, with no create/update/delete, spatial analysis, or broader dataset listing operations—so the named domain is notably incomplete.