Skip to main content
Glama

Arcgis Pittsburgh

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

City of Pittsburgh GIS — Pittsburgh, Pennsylvania 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
47.1% over 38 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-arcgis-pittsburgh
GitHub Stars
0
Server Listing
arcgis-pittsburgh

TDQS

A3.7/5.0

Scored across 34 tools

Disambiguation2/5

Several tools have overlapping or indistinct purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are variations of the same router (beta is currently identical to stable), and discover_tools, suggest_questions, and pipeworx_trending all serve discovery. The many meta-research tools (deep_research, validate_claim, compare_entities, entity_profile, recent_changes) also have fuzzy boundaries that require careful reading to avoid misselection.

Naming Consistency4/5

Nearly all tools use a consistent snake_case convention (e.g. ask_pipeworx, entity_profile, polymarket_edges, search_datasets). Minor deviations appear in compound names like ai_visibility_check and generate_llms_txt, but the overall pattern is predictable and readable.

Tool Count2/5

With 34 tools, the set is heavy for a server named 'Arcgis Pittsburgh'. Only three tools (search_datasets, layer_info, query_layer) relate to Pittsburgh GIS, while the remaining 31 are broad Pipeworx data/research/meta tools, creating a severe mismatch between the apparent scope and the actual tool count.

Completeness3/5

For Pittsburgh GIS, the surface offers dataset search, layer schema inspection, and attribute querying, which covers basic read-only exploration. However, there are notable gaps: no create/update/delete operations for features, no spatial analysis or geocoding, and no tools to list all layers within a service or export data, which will cause dead ends for common GIS workflows.

Tool Schema Changelog

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

  1. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "market": "will-bitcoin-reach-100k-in-july-2026"
-  },
-  {
-    "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
-  }
-]New value: +[
+  {
+    "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  },
+  {
+    "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  }
+]
      • changedInput schema / properties / market / description
        Previous value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
    • Changedpolymarket_kalshi_spread2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "topic": "fed"
-  },
-  {
-    "topic": "btc"
-  }
-]New value: +[
+  {
+    "topic": "fed"
+  },
+  {
+    "topic": "btc"
+  },
+  {
+    "topic": "bitcoin"
+  },
+  {
+    "topic": "fed rate decision"
+  }
+]
      • changedInput schema / properties / topic / description
        Previous value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."

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