Utah state open data via Socrata SoQL — government, grants, health, demographics.
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 34 tools
Several tool families overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route questions to the same data, and the six polymarket_* tools plus entity_profile/compare_entities/recent_changes/validate_claim share domains. Descriptions work hard to differentiate them, but an agent still faces real risk of picking the wrong variant, especially since ask_pipeworx_beta is documented as currently identical to ask_pipeworx.
Every tool uses snake_case with a largely verb_noun or consistent prefix pattern (compare_entities, resolve_entity, polymarket_*, ask_pipeworx_*), so the convention is predictable. A few bare-noun tools (datasets, metadata, query, recall, remember, forget) are minor deviations but still readable and non-chaotic.
At 34 tools the set is heavy for what the server name implies (Utah Open Data alone would need only datasets/metadata/query). The bulk is a broad, multi-domain Pipeworx platform suite, so the count is bloated relative to the apparent stated purpose and pushes past the 25+ threshold, with redundant variants like ask_pipeworx_beta adding little.
Coverage is broad and read-oriented (data lookup, entity resolution, research, memory CRUD, subscriptions, feedback), and the three Utah-specific tools (datasets, metadata, query) form a coherent read-only slice. However, the set is a grab-bag serving no single clear domain, so it is neither cleanly complete for Utah Open Data nor fully coherent as one tool surface.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
bet_research2 fields changedInput schema / examplesPrevious value: -[
- {
- "market": "when-will-bitcoin-hit-150k"
- },
- {
- "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
- }
-]New value: +[
+ {
+ "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
+ },
+ {
+ "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
+ }
+]Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."polymarket_kalshi_spread1 field changedInput schema / examplesPrevious value: -[
- {
- "topic": "fed"
- },
- {
- "topic": "btc"
- }
-]New value: +[
+ {
+ "topic": "fed"
+ },
+ {
+ "topic": "btc"
+ },
+ {
+ "topic": "bitcoin"
+ },
+ {
+ "topic": "fed rate decision"
+ }
+]bet_research2 fields changedInput schema / examplesPrevious value: -[
- {
- "market": "will-bitcoin-reach-100k-in-july-2026"
- },
- {
- "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
- }
-]New value: +[
+ {
+ "market": "when-will-bitcoin-hit-150k"
+ },
+ {
+ "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
+ }
+]Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."polymarket_kalshi_spread1 field changedInput schema / properties / topic / descriptionPrevious value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."Oregon Open Data — US government open data (data.oregon.gov) via the Socrata SoQL API: state…
Washington State Open Data — US government open data (data.wa.gov) via the Socrata SoQL API: state…
Texas Open Data — US government open data (data.texas.gov) via the Socrata SoQL API: state…
Connecticut Open Data — US government open data (data.ct.gov) via the Socrata SoQL API: state…
Add one secure layer between your agents and this server.