Skip to main content
Glama

Server Details

City of Lakeland GIS — Lakeland, Florida 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-lakeland
GitHub Stars
0
Server Listing
mcp-arcgis-lakeland
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 47 tools

Disambiguation2/5

Several clusters are near-indistinguishable: ask_pipeworx, ask_pipeworx_beta (which the description admits currently behaves identically), ask_pipeworx_grounded and deep_research all route the same question, and discover_tools/suggest_questions both exist to reveal the catalog. The prediction-market block (polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread, bet_research, updown_venue_compare, updown_divergence_rate, prediction_calibration, resolution_audit, resolution_diff) forces the agent to read long descriptions to pick correctly. Only the three GIS tools and the memory tools (remember/recall/forget) are cleanly separable.

Naming Consistency3/5

All names are snake_case, which avoids the worst outcome, but the verb/noun convention varies: verb_noun (search_datasets, query_layer, compare_entities, validate_claim, scan_dependency) sits beside bare noun phrases (entity_profile, company_facts, prediction_calibration, resolution_audit, pipeworx_trending) and prefixed families (ask_pipeworx*, polymarket_*, updown_*). Readable, but not a predictable pattern an agent can generalize from.

Tool Count2/5

47 tools is far past the point of a well-scoped surface, and it is wildly disproportionate to a server labelled 'Arcgis Lakeland' whose actual GIS scope is three tools. The remaining ~44 are a general Pipeworx data/markets catalog bolted onto a municipal GIS server, so the set is heavy and thematically incoherent rather than expansive-for-a-reason.

Completeness2/5

For the apparent domain (City of Lakeland GIS), the surface is create-free and thin: search_datasets, layer_info and query_layer cover discovery and read, but there is no geocoding, spatial/geometry filtering, map or tile export, or any write operation, so most GIS workflows dead-end. The unrelated Pipeworx breadth does not compensate, because it lies outside the server's stated 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.