Skip to main content
Glama

Server Details

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

The last two health checks of this connector failed. 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
Uptime
0.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-arcgis-austin
GitHub Stars
0
Server Listing
mcp-arcgis-austin
ChatGPT
–
Claude
–

TDQS

A3.6/5.0

Scored across 47 tools

Disambiguation3/5

Within the ArcGIS trio (search_datasets, layer_info, query_layer) the boundaries are clean, but the other 44 tools contain heavily overlapping entry points: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools and suggest_questions all plausibly claim 'start here', and entity_profile vs company_facts vs compare_entities vs recent_changes vs company_register_search vs resolve_entity require reading long descriptions to separate. The Polymarket family (bet_research, polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, polymarket_edge_tracker, polymarket_kalshi_spread, resolution_audit, resolution_diff, updown_*) is at least articulated by descriptions, but selection still demands careful reading rather than obvious naming.

Naming Consistency4/5

Nearly everything is lowercase snake_case with a verb_noun or noun_noun shape (search_datasets, query_layer, company_register_search, polymarket_fill_risk, resolution_audit), which is predictable and readable. The deviations are minor and local: single-word verbs (remember, recall, forget, subscribe, unsubscribe) and suffix variants (ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded) that read more as versioning than as distinct operations.

Tool Count1/5

The server is named 'Arcgis Austin' yet only three of 47 tools (search_datasets, layer_info, query_layer) touch Austin GIS data; the remaining 44 are a broad Pipeworx data-gateway catalog spanning SEC filings, prediction markets, LLM visibility auditing, npm dependency scanning and CRM-style row research. That is both an extreme scope mismatch for the stated purpose and well past the 25+ threshold where a set becomes unwieldy.

Completeness2/5

For the apparent ArcGIS Austin domain the surface is thin: you can search datasets, inspect a layer schema, and run a single where-clause query, but there is no geometry/spatial filter, no aggregation or statistics, no geocoding, no export, and no write operations. The unrelated bulk of the catalog does not compensate, since almost none of it extends the GIS capability a caller would expect from this server name.

Tool Schema Changelog

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

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.