Skip to main content
Glama

Server Details

Tallahassee-Leon County GIS — Tallahassee-Leon County, 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-tallahassee
GitHub Stars
0
Server Listing
arcgis-tallahassee
ChatGPT
–
Claude
–

TDQS

A3.9/5.0

Scored across 47 tools

Disambiguation2/5

The set contains several near-duplicate clusters: ask_pipeworx / ask_pipeworx_beta are explicitly stated to behave identically right now, ask_pipeworx_grounded and deep_research also answer questions, and ai_visibility_check vs scan_competitor_ai_presence overlap. The prediction-market family (polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread, bet_research, kalshi_weather_edge, resolution_audit/diff) is heavily populated with tools whose boundaries are argued in prose rather than being self-evident. Descriptions try hard to disambiguate, but an agent must read paragraphs to pick correctly.

Naming Consistency4/5

All 47 names are snake_case, which is a strong, predictable base convention. The main deviations are noun-first names (company_facts, entity_profile, resolution_audit, prediction_calibration) alongside verb-first ones (query_layer, resolve_entity, validate_claim), plus a 'beta' suffix variant of an existing tool.

Tool Count2/5

47 tools is far beyond the stated scope of an ArcGIS Tallahassee GIS server, which only requires search_datasets, layer_info and query_layer. The remainder is a general-purpose data/analytics gateway (SEC, prediction markets, LLM visibility probes, memory, subscriptions) bolted onto a municipal GIS server.

Completeness3/5

For the apparent GIS domain the surface covers discovery (search_datasets), schema (layer_info) and attribute querying (query_layer), which is a workable read-only path. However there is no spatial/envelope filter, no geometry-intersect query, no counting or distinct-value helper, and no listing of layers within a service — common GIS agent needs that will produce workarounds or failures.

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.