Skip to main content
Glama

Server Details

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

TDQS

A3.7/5.0

Scored across 47 tools

Disambiguation2/5

Several clusters have fuzzy boundaries: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research / discover_tools / suggest_questions all answer "route my question to a source," and the ~12 prediction-market tools (polymarket_edges vs polymarket_arbitrage vs polymarket_kalshi_spread vs bet_research vs polymarket_fill_risk vs polymarket_edge_tracker) overlap heavily despite long descriptions. Descriptions do disambiguate when read carefully, but an agent skimming the list will misselect.

Naming Consistency3/5

Everything is snake_case, so there is no camelCase chaos, but the conventions are mixed: verb_noun (query_layer, search_datasets, resolve_entity, validate_claim), noun_noun (company_facts, entity_profile, prediction_calibration), and noun_verb (ai_visibility_check, updown_divergence_rate). Readable but not predictable.

Tool Count1/5

47 tools for a server named 'Arcgis Tampa' is a severe mismatch — only search_datasets, layer_info, and query_layer relate to Tampa GIS; the remaining 44 are a general Pipeworx data gateway (SEC, FRED, Polymarket, memory, subscriptions). The scope is wildly beyond the stated purpose.

Completeness3/5

The GIS surface covers a usable read-only pipeline (keyword search -> schema -> SQL query), but has notable gaps: no way to enumerate all layers in a feature service, no spatial/geometry filtering (only `where`), no aggregate/statistics, no export, and no write operations. Separately, the huge unrelated tool mass makes the overall surface incoherent rather than methodically complete.

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.