Skip to main content
Glama

Server Details

City of Tempe GIS — Tempe, Arizona 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-tempe
GitHub Stars
0
Server Listing
mcp-arcgis-tempe
ChatGPT
–
Claude
–

TDQS

A3.9/5.0

Scored across 47 tools

Disambiguation3/5

The set is organized into recognizable families (ArcGIS, Pipeworx research, prediction markets, memory/subscriptions), and many descriptions give explicit routing guidance. However, several tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all serve as entry points, while polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, and bet_research overlap heavily. Agents can usually route correctly with effort, but the boundaries are not clean.

Naming Consistency4/5

Nearly every tool name is snake_case, which keeps the set visually consistent. The main inconsistency is grammatical pattern: some names are verb-led (validate_claim, resolve_entity, search_datasets), others are noun-led (entity_profile, company_facts, prediction_calibration), and some are domain-prefixed (polymarket_*, updown_*). This is readable but not a single predictable convention.

Tool Count2/5

Forty-seven tools is far too many for a server named 'Arcgis Tempe', especially since only search_datasets, layer_info, and query_layer are actually GIS tools. The remaining catalog is a broad general-purpose data/research platform, so the tool count is not scoped to the apparent server purpose. It is not the absolute worst case, but it is heavily overstuffed.

Completeness2/5

For the stated ArcGIS/Tempe GIS purpose, the surface is thin: it supports dataset search, schema inspection, and attribute queries, but lacks geocoding, spatial filters, statistics, joins, or export operations that a GIS user would expect. The rest of the tools address unrelated domains, so they do not complete the GIS workflow. The overall set is broad but not complete for any one coherent purpose.

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.