Skip to main content
Glama

Arcgis Fallschurch

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

City of Falls Church GIS — Falls Church, Virginia 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
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-arcgis-fallschurch
GitHub Stars
0
Server Listing
mcp-arcgis-fallschurch

TDQS

A3.8/5.0

Scored across 34 tools

Disambiguation3/5

The ArcGIS trio (search_datasets, layer_info, query_layer) is cleanly separated, but the set contains several overlapping families: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research all answer research questions, and ai_visibility_check overlaps with scan_competitor_ai_presence. Detailed routing guidance helps, but an agent still faces redundant choices for the same task.

Naming Consistency4/5

Names are uniformly snake_case with no camelCase or casing chaos, which keeps the set readable. However the pattern is not a strict verb_noun convention: it mixes action names (ask_pipeworx, query_layer, remember), noun phrases (entity_profile, layer_info, recent_alerts) and noun_verb compounds (ai_visibility_check).

Tool Count2/5

34 tools is heavy for the apparent ArcGIS Falls Church scope, and only 3 tools (search_datasets, layer_info, query_layer) directly serve that GIS purpose. The remaining 31 are general Pipeworx gateway tools, with several redundant variants (three ask_pipeworx modes, five polymarket tools) inflating the surface.

Completeness3/5

For the GIS query use case, the surface covers discovery (search_datasets), schema inspection (layer_info) and feature querying (query_layer), which is a reasonable read-only path. But it lacks obvious GIS support operations such as enumerating layers within a Feature Service, spatial/geometric queries beyond where clauses, and service-level metadata, so agents can hit a dead end.

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