Skip to main content
Glama

Server Details

City of Kingston GIS — Kingston, Ontario (Canada) 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-kingston
GitHub Stars
0
Server Listing
mcp-arcgis-kingston
ChatGPT
–
Claude
–

TDQS

A3.8/5.0

Scored across 47 tools

Disambiguation2/5

The set contains large clusters of overlapping tools: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools and suggest_questions all route/answer questions across the same catalog (beta is explicitly identical to ask_pipeworx today), and thirteen prediction-market tools (polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread, bet_research, kalshi_weather_edge, prediction_calibration, updown_venue_compare, updown_divergence_rate, resolution_audit, resolution_diff, release_calendar_markets) differ only by subtle framing. Individual descriptions are unusually detailed about when to prefer one over another, which helps, but an agent choosing among 47 tools will still misselect within these families.

Naming Consistency4/5

Every name is snake_case with no camelCase or mixed-style outliers, and domain families carry consistent prefixes (polymarket_*, updown_*, ask_pipeworx_*, pipeworx_*). The pattern is not strictly verb_noun throughout (compare_entities/query_layer vs entity_profile/company_facts/kalshi_weather_edge), but the deviations are systematic rather than chaotic.

Tool Count2/5

47 tools is far too many for a server presented as 'Arcgis Kingston' — only search_datasets, layer_info and query_layer relate to that purpose, while the other 44 form a general Pipeworx data/markets aggregator. The surface is both oversized and mis-scoped relative to the stated server identity.

Completeness2/5

For the apparent GIS domain the surface is thin: search, layer schema and an attribute-only query with no spatial/geometry filter, no statistics or aggregation, no export, and no write operations, so many GIS workflows hit dead ends. The aggregator side is broad but largely irrelevant to the named purpose, so overall coverage for the advertised domain is poor.

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.