Skip to main content
Glama

Arcgis Austin

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

City of Austin GIS — Austin, Texas open geospatial data (ArcGIS).

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.

Status
Unhealthy
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-arcgis-austin
GitHub Stars
0
Server Listing
mcp-arcgis-austin

TDQS

A3.5/5.0

Scored across 38 tools

Disambiguation2/5

The server mixes two unrelated domains: ArcGIS Austin geospatial tools (search_datasets, query_layer, layer_info) and a massive Pipeworx data/prediction-market toolkit. Within the Pipeworx cluster, several tools overlap heavily (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, validate_claim), and the polymarket_* family has multiple edge-finding tools that could be confused. The ArcGIS tools are distinct but are a tiny minority.

Naming Consistency2/5

Naming is inconsistent across the set: some tools use verb_noun (search_datasets, query_layer, layer_info, resolve_entity, validate_claim), but many use product-specific or vague names (ask_pipeworx, bet_research, polymarket_edges, pipeworx_trending, remember/recall/forget). The polymarket_* family is consistent, but the overall set mixes conventions and brand names.

Tool Count2/5

38 tools is heavy, and the vast majority belong to a general-purpose data/prediction-market platform rather than the ArcGIS Austin domain implied by the server name. The three ArcGIS tools are a small island in a sea of unrelated functionality, making the set feel bloated and unfocused.

Completeness2/5

For the ArcGIS Austin domain, the surface is thin: search, layer info, and query exist, but there is no way to create, update, or delete data, and no handling of maps, geocoding, or analysis. For the Pipeworx domain, coverage is broad but the server's stated purpose is unclear, and the ArcGIS tools appear to be an afterthought.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 4 tool updates
    • Addedkalshi_weather_edge
    • Addedrelease_calendar_markets
    • Addedresolution_audit
    • Addedresolution_diff
  2. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous 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": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  },
+  {
+    "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  }
+]
      • changedInput schema / properties / market / description
        Previous 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 (\"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."
    • Changedpolymarket_kalshi_spread2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "topic": "fed"
-  },
-  {
-    "topic": "btc"
-  }
-]New value: +[
+  {
+    "topic": "fed"
+  },
+  {
+    "topic": "btc"
+  },
+  {
+    "topic": "bitcoin"
+  },
+  {
+    "topic": "fed rate decision"
+  }
+]
      • changedInput schema / properties / topic / description
        Previous 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."

Related MCP Connectors

Related MCP Servers

Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources