Skip to main content
Glama

Server Details

Kansas State GIS — Kansas 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-kansas
GitHub Stars
0
Server Listing
arcgis-kansas
ChatGPT
–
Claude
–

TDQS

A3.8/5.0

Scored across 47 tools

Disambiguation2/5

Several clusters are genuinely hard to separate at selection time: ask_pipeworx / ask_pipeworx_beta (documented as currently identical) / ask_pipeworx_grounded / deep_research / discover_tools / suggest_questions all answer 'find me data', and polymarket_arbitrage vs polymarket_edges vs polymarket_edge_tracker vs polymarket_fill_risk vs bet_research overlap heavily around 'is there an edge in this market'. The extremely long descriptions do a lot of disambiguating work (e.g. company_facts explicitly overrides entity_profile), which keeps this above the floor, but with 47 tools an agent still faces multiple plausible pick-one choices per request.

Naming Consistency4/5

Everything is lower snake_case with no camelCase or style mixing, and product families are prefixed coherently (polymarket_*, updown_*, pipeworx_*, kalshi_*). The convention varies between verb_noun (search_datasets, resolve_entity, validate_claim) and noun_noun (entity_profile, prediction_calibration, company_facts), so it is readable and predictable rather than a strict single pattern.

Tool Count2/5

47 tools is far past the well-scoped range, and for a server named 'Arcgis Kansas' only three tools (search_datasets, query_layer, layer_info) serve that purpose while 44 belong to an unrelated general data/prediction-market platform. Individual tools are substantive rather than filler, but the surface is badly oversized relative to the advertised scope.

Completeness2/5

For the stated GIS domain the surface is thin: you can find a layer's schema and run attribute/SQL queries, but there is no spatial filter (bbox, intersects, distance), no aggregation/statistics or feature-count query, no map/export/tile or geocoding operation — a real GIS workflow hits an immediate dead end. The unrelated Pipeworx tools are internally fairly complete, but they do not cover the server's apparent purpose.

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.