Skip to main content
Glama

Arcgis Tulsa

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

City of Tulsa GIS — Tulsa, Oklahoma open geospatial data (ArcGIS).

Glama couldn't complete the latest health check. 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.2% over 24 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-arcgis-tulsa
GitHub Stars
0
Server Listing
mcp-arcgis-tulsa

TDQS

A3.8/5.0

Scored across 39 tools

Disambiguation3/5

Several clusters overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools and suggest_questions all route questions to data with only subtle differentiators, and the polymarket family (edges, arbitrage, fill_risk, edge_tracker, kalshi_spread, bet_research) requires reading dense prose to separate. ai_visibility_check vs scan_competitor_ai_presence and search_datasets vs discover_tools also overlap. Descriptions are extremely detailed and do disambiguate in most cases, but the boundaries are blurred enough that misselection is plausible.

Naming Consistency4/5

All 39 names use consistent snake_case (no camelCase or hyphen mixing), which is the primary consistency criterion. The pattern is not strictly verb_noun—there is a mix of verb-only (remember, recall, forget, subscribe), noun phrases (entity_profile, company_facts), and verb_noun (list_subscriptions, query_layer, resolve_entity)—but the stylistic convention is uniform and readable.

Tool Count2/5

At 39 tools this exceeds the heavy threshold, and many are redundant meta-tools or near-duplicate market-scanning variants that could be consolidated. For a server named after a GIS dataset collection, exposing a full multi-domain aggregator surface is a large mismatch with the apparent purpose.

Completeness3/5

Coverage is uneven across the mixed domains: memory (remember/recall/forget), subscriptions (subscribe/list_subscriptions/unsubscribe/recent_alerts), and market resolution (resolution_audit/diff) are complete, but the GIS side is read-only with no create/update/delete for features or layers. The broad surface has notable per-domain gaps rather than a clean lifecycle.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedrelease_calendar_markets2 fields changed
      • addedOutput schema / properties / empty_reason
        Added value: +{
+  "description": "Present ONLY on a zero-release window: \"no_releases_in_window\". The window was queried and nothing is scheduled — this is an answer, not a failure.",
+  "type": "string"
+}
      • addedOutput schema / properties / hint
        Added value: +{
+  "description": "Present ONLY on a zero-release window: what to change (usually a wider `hours`).",
+  "type": "string"
+}
  2. 39 tool updates
    • First observedai_visibility_check
    • First observedask_pipeworx
    • First observedask_pipeworx_beta
    • First observedask_pipeworx_grounded
    • First observedbet_research
    • First observedcompany_facts
    • First observedcompare_entities
    • First observeddeep_research
    • First observeddiscover_tools
    • First observedentity_profile
    • First observedforget
    • First observedgenerate_llms_txt
    • First observedkalshi_weather_edge
    • First observedlayer_info
    • First observedlist_subscriptions
    • First observedpipeworx_feedback
    • First observedpipeworx_trending
    • First observedpolymarket_arbitrage
    • First observedpolymarket_edge_tracker
    • First observedpolymarket_edges
    • First observedpolymarket_fill_risk
    • First observedpolymarket_kalshi_spread
    • First observedquery_layer
    • First observedrecall
    • First observedrecent_alerts
    • First observedrecent_changes
    • First observedrelease_calendar_markets
    • First observedremember
    • First observedresolution_audit
    • First observedresolution_diff
    • First observedresolve_entity
    • First observedscan_competitor_ai_presence
    • First observedscan_dependency
    • First observedsearch_datasets
    • First observedsearch_within
    • First observedsubscribe
    • First observedsuggest_questions
    • First observedunsubscribe
    • First observedvalidate_claim

Related MCP Connectors

Related MCP Servers

Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources