Skip to main content
Glama

Server Details

City of Novi GIS — Novi, Michigan 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-novi
GitHub Stars
0
Server Listing
mcp-arcgis-novi
ChatGPT
–
Claude
–

TDQS

A3.8/5.0

Scored across 47 tools

Disambiguation2/5

Several clusters have unclear boundaries: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research all route the same question to the same catalog (the beta tool openly states it currently matches the stable one), and discover_tools / suggest_questions / search_datasets all answer 'what tools/data exist'. The prediction-markets cluster is worse — bet_research, polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread and release_calendar_markets all overlap on 'is there an edge here', with the distinctions explained only by very long prose. Only the three genuine GIS tools (search_datasets, layer_info, query_layer) are cleanly separable.

Naming Consistency4/5

Everything is consistently snake_case with no camelCase mixing, and namespace prefixes (polymarket_, updown_, archive_, ask_pipeworx_) are applied regularly. The only deviation is verb ordering — verb-first (query_layer, resolve_entity, validate_claim, compare_entities) mixed with noun-first (company_facts, entity_profile, bet_research, prediction_calibration, layer_info) — which is readable but not a single predictable pattern.

Tool Count2/5

47 tools for a server named 'Arcgis Novi' whose apparent purpose (City of Novi GIS parcels/zoning) is served by exactly 3 of them. The remaining 44 are general Pipeworx platform, memory, subscription, prediction-market and research tools, so the surface is roughly an order of magnitude larger than the stated scope warrants.

Completeness2/5

The GIS surface is search_datasets -> layer_info -> query_layer and then stops: there is no way to enumerate the layers/services inside a returned Feature Service URL, no spatial/bbox or intersects filter, no export to GeoJSON, and no metadata beyond fields/geometry type. The broader surface, while enormous, is also uneven for the stated domain — the memory, subscription and feedback tools are unrelated to GIS, and the naming of the server implies one thing while the tools deliver another.

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.