Arcgis Sacramento
Server Details
City of Sacramento GIS — Sacramento, California 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-sacramento
- GitHub Stars
- 0
- Server Listing
- mcp-arcgis-sacramento
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 47 tools
ask_pipeworx_beta is explicitly documented as behaving identically to ask_pipeworx, and the universal router ask_pipeworx is also positioned as the 'default entry point' for the same questions that entity_profile, company_facts, validate_claim, recent_changes, compare_entities and deep_research each specialize in, so selection boundaries are fuzzy. The prediction-market cluster (bet_research, polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, release_calendar_markets) is large and partially overlapping for a 'what should I bet on' question. Only the ArcGIS trio (search_datasets / layer_info / query_layer) and archive_evidence vs archive_compare are cleanly separable.
Nearly all 47 names are lower snake_case with a recognizable verb_noun or domain_qualifier shape (search_datasets, query_layer, resolve_entity, compare_entities, scan_dependency, updown_venue_compare), and the ask_pipeworx / _grounded / _beta family is a deliberate suffix pattern. The deviations are noun-phrase names (entity_profile, company_facts, recent_changes, prediction_calibration, polymarket_edges), which are still readable and predictable in spirit.
47 tools for a server named 'Arcgis Sacramento' is a severe mismatch: only three tools (search_datasets, layer_info, query_layer) have anything to do with Sacramento GIS, and the remaining 44 are a general-purpose Pipeworx data/markets/agent-memory surface. Far past the 25-tool heavy threshold, with whole clusters (eleven prediction-market tools, several LLM-routing meta-tools) that no single agent session will need together.
For the stated ArcGIS domain the surface is thin: you can search datasets, read a layer schema and run an attribute query, but there is no geometry/bbox spatial query, no spatial-relationship predicate, no export or tiling operation, and no way to list a whole service's layers in one call. Meanwhile the extra 44 tools, while individually broad, do not complete the GIS workflow and mostly belong to an unrelated catalog.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
City of San Jose GIS — San Jose, California open geospatial data (ArcGIS).
City of San Bernardino GIS — San Bernardino, California open geospatial data (ArcGIS).
City of Richmond GIS — Richmond, Virginia open geospatial data (ArcGIS).
City of Salem GIS — Salem, Oregon open geospatial data (ArcGIS).
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceCity of San Bernardino GIS — San Bernardino, California open geospatial data (ArcGIS).89 npmMIT
- AlicenseNot gradedqualityCmaintenanceSarpy County GIS — Sarpy County, Nebraska open geospatial data (ArcGIS).87 npmMIT
- AlicenseNot gradedqualityCmaintenanceMono County GIS — Mono County & Mammoth Lakes, California open geospatial data (ArcGIS).90 npmMIT
- AlicenseNot gradedqualityCmaintenanceLincoln County GIS — Lincoln County, North Carolina open geospatial data (ArcGIS).69 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.