Skip to main content
Glama

Server Details

City of Johnson City GIS — Johnson City, Tennessee 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-johnsoncity
GitHub Stars
0
Server Listing
mcp-arcgis-johnsoncity
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 47 tools

Disambiguation2/5

There are large clusters of near-duplicate tools: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research / discover_tools / suggest_questions all claim to be the 'entry point' or 'start here' for questioning, and beta is explicitly self-described as identical to ask_pipeworx. The prediction-market cluster (polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread, bet_research, kalshi_weather_edge, prediction_calibration, updown_venue_compare, updown_divergence_rate, release_calendar_markets) has real boundaries but so many adjacent options that misselection is likely. Only the three ArcGIS tools (search_datasets, query_layer, layer_info) are cleanly separable.

Naming Consistency3/5

Naming is consistently snake_case with no camelCase mixing, which helps. However conventions vary: verb_noun (query_layer, search_datasets, resolve_entity), noun_phrase (entity_profile, company_facts, polymarket_edges), and bare verbs (remember, recall, forget) coexist without a single predictable pattern, and the ask_pipeworx family adds suffix-based variants rather than distinct verbs.

Tool Count2/5

47 tools is far past the 15-tool band and is only barely under the 50+ extreme, with several tools explicitly redundant (beta router, suggest_questions vs discover_tools). More importantly the count is wildly disproportionate to the server's stated purpose: a City of Johnson City GIS server only justifies three of these tools.

Completeness2/5

For the apparent domain (Johnson City GIS feature services) the surface is read-only: search, schema, and attribute query exist, but there is no spatial/filter-by-geometry query, no geocoding, no map/export, and no update or publish path — agents working in that domain will hit dead ends. The surrounding Pipeworx tools are each individually rich but are clearly a different product bolted onto this server, so they do not compensate for the GIS gap.

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.