Skip to main content
Glama

Server Details

City of Detroit GIS — Detroit, 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-detroit
GitHub Stars
0
Server Listing
arcgis-detroit
ChatGPT
–
Claude
–

TDQS

A3.8/5.0

Scored across 47 tools

Disambiguation2/5

Several clusters are genuinely hard to separate: ask_pipeworx, ask_pipeworx_beta (admittedly 'matches ask_pipeworx exactly' right now), ask_pipeworx_grounded and deep_research all claim to be the default entry point for factual questions, and polymarket_edges / polymarket_arbitrage / polymarket_fill_risk / polymarket_edge_tracker / bet_research all overlap on 'find and size a Polymarket trade'. entity_profile, company_facts, compare_entities and recent_changes also blur ('tell me about X' vs 'facts for period X' vs 'X vs Y' vs 'what's new with X'), and the very long descriptions, while detailed, make the boundary harder to scan rather than clearer. The ArcGIS trio (search_datasets / layer_info / query_layer) is cleanly separated, but that is a small minority of the set.

Naming Consistency3/5

Everything is snake_case and readable, but the convention is mixed: some tools are verb_noun (query_layer, resolve_entity, validate_claim, compare_entities, search_within), many are noun-first or noun-only (company_facts, entity_profile, recent_alerts, recent_changes, prediction_calibration, layer_info, bet_research), and only some families carry a domain prefix (polymarket_*, updown_*, ask_pipeworx_*). Readable throughout, but a caller cannot predict a tool's name from its action.

Tool Count2/5

47 tools is well past the point where each one earns its place, and the surface is far broader than the server's stated purpose ('Arcgis Detroit' — only search_datasets, layer_info and query_layer relate to it). The remainder is an unrelated grab-bag of finance, pharma, prediction-market, memory, subscription and meta-discovery tools, including a beta duplicate of the router.

Completeness3/5

For the Detroit GIS domain suggested by the server name, the surface is thin: search → inspect schema → attribute-filter query covers browsing, but there is no spatial/bbox query, no list-all-layers for a service, no statistics/aggregate, and no map/feature export, so spatial questions dead-end. As a general Pipeworx data gateway the coverage is broad (SEC, FRED, FDA, patents, weather, markets), though gaps like forward-looking court calendars are acknowledged as unsupported.

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.