Skip to main content
Glama

Server Details

City of Coquitlam GIS — Coquitlam, BC (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-coquitlam
GitHub Stars
0
Server Listing
mcp-arcgis-coquitlam
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 47 tools

Disambiguation2/5

Several clusters have genuinely unclear boundaries: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools and suggest_questions all compete as a generic entry point, and entity_profile / company_facts / compare_entities / recent_changes / resolve_entity / company_register_search all answer 'tell me about this company'. The prediction-market surface is even denser, with bet_research, polymarket_edges, polymarket_arbitrage, polymarket_kalshi_spread, polymarket_fill_risk, release_calendar_markets and three updown/resolution tools whose selection depends on prose caveats rather than distinct purposes. Descriptions do include heavy 'prefer X over Y' steering, which helps, but the boundaries are drawn by policy text rather than by the tools themselves.

Naming Consistency3/5

Casing is uniformly snake_case, which is a real strength, but the grammatical pattern is mixed: verb_noun (query_layer, search_datasets, resolve_entity, generate_llms_txt) alongside bare noun phrases (entity_profile, company_facts, bet_research, prediction_calibration, layer_info, pipeworx_trending, recent_alerts). Suffixes like _beta and _row add further ad-hoc variation, and the three ask_pipeworx variants differ only by a qualifier rather than by a distinct verb.

Tool Count1/5

47 tools is far past the point where an agent can hold the set in view, and it is wildly over-scoped for a server named 'Arcgis Coquitlam', of which only search_datasets, layer_info and query_layer correspond to Coquitlam GIS. The remainder (SEC/XBRL financials, Polymarket arbitrage, Kalshi weather, LLM brand probes, npm dependency scanning, memory and subscription management) belongs to other products entirely.

Completeness3/5

For the apparent GIS domain the trio search_datasets → layer_info → query_layer covers discovery, schema inspection and row retrieval, which is a workable read-only surface for an open-data portal. However there is no spatial filter (bounding box/geometry predicate), no aggregate/statistics operation, and no export or pagination-cursor guidance beyond limit/offset, so non-trivial spatial questions dead-end.

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.