Skip to main content
Glama

Arcgis Lorain

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Lorain County GIS — Lorain County, Ohio 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
42.5% over 41 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-arcgis-lorain
GitHub Stars
0
Server Listing
mcp-arcgis-lorain

TDQS

A3.9/5.0

Scored across 34 tools

Disambiguation3/5

Most tools target distinct workflows, but there are real overlaps: ask_pipeworx, ask_pipeworx_beta (explicitly identical right now), and ask_pipeworx_grounded form a family an agent could easily confuse; discover_tools vs suggest_questions both serve tool discovery; and the five polymarket_* tools (arbitrage, edges, edge_tracker, fill_risk, kalshi_spread) partly overlap in 'find opportunities'. Descriptions are unusually detailed and mostly disambiguate, but the boundaries require careful reading.

Naming Consistency4/5

Overwhelmingly consistent snake_case verb_noun / noun patterns (validate_claim, resolve_entity, compare_entities, search_datasets, remember/recall/forget, subscribe/unsubscribe). Minor deviation in the ask_pipeworx / _beta / _grounded suffix scheme and a few noun-style names (entity_profile, layer_info, recent_changes), but nothing chaotic.

Tool Count2/5

34 tools is well past the heavy threshold. While the server aggregates many domains, there is clear redundancy worth pruning — three ask_pipeworx variants (one currently identical) and five polymarket tools for overlapping 'find/verify edges' work. The count feels bloated rather than tightly scoped.

Completeness4/5

As a universal data/research gateway the surface is quite complete: query (ask_pipeworx family, deep_research), entity resolution, profiles, comparison, claim validation, memory CRUD (remember/recall/forget), subscription lifecycle (subscribe/unsubscribe/recent_alerts/list_subscriptions), feedback, trending, and discovery. Gaps are minor — e.g. the ArcGIS tools (search_datasets, layer_info, query_layer) are read-only with no write/maintenance path, but agents can work around this.

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