Skip to main content
Glama

Server Details

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

TDQS

A3.9/5.0

Scored across 47 tools

Disambiguation2/5

Several clusters have fuzzy boundaries: ask_pipeworx / ask_pipeworx_beta (explicitly identical) / ask_pipeworx_grounded / deep_research all claim to be the routing entry point, and polymarket_edges / polymarket_arbitrage / polymarket_edge_tracker / bet_research all scan for the same kind of mispricing. Company tools (entity_profile vs company_facts vs compare_entities vs recent_changes) are distinguished only by long prose, and discover_tools vs suggest_questions serve near-identical discovery needs. A few tools (archive_compare/archive_evidence, remember/recall/forget) are cleanly separable, but the set overall forces the agent to read essays to pick correctly.

Naming Consistency4/5

Every name is lowercase snake_case with no camelCase mixing, so the surface is mechanically predictable. Verb style varies (verb_noun like resolve_entity/validate_claim vs noun-phrase like entity_profile/layer_info/deep_research) and there are suffix variants (ask_pipeworx_beta, _grounded), but nothing unreadable or chaotic.

Tool Count2/5

47 tools for a server described as City of McKinney ArcGIS open data — only search_datasets, layer_info and query_layer relate to that purpose; the other 44 are a general-purpose finance/prediction-market/AI-marketing gateway. Far past the 25-tool threshold and the mismatch with the stated scope is severe.

Completeness3/5

The GIS read path (search_datasets → layer_info → query_layer) is coherent and covers discovery, schema and attribute querying, so an agent can retrieve McKinney parcel/zoning data. Notable gaps remain: no spatial predicate or geometry-envelope filtering, no geocoding, no statistics/aggregate or per-service layer listing, leaving spatial questions that an ArcGIS portal should answer unanswerable.

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.