Skip to main content
Glama

Server Details

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

TDQS

A3.8/5.0

Scored across 34 tools

Disambiguation3/5

Several tool clusters overlap heavily: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded are near-identical routers (beta explicitly 'matches ask_pipeworx exactly'), polymarket_arbitrage and polymarket_edges both scan for opportunities, and discover_tools vs suggest_questions both serve catalog discovery. The verbose descriptions provide strong routing guidance, which rescues the set somewhat, but the boundaries are genuinely fuzzy in places. ai_visibility_check vs scan_competitor_ai_presence is a milder instance of the same problem.

Naming Consistency4/5

Nearly all names follow snake_case with a verb_noun or noun_qualifier pattern (ask_pipeworx, resolve_entity, validate_claim, query_layer, search_datasets, entity_profile, recent_changes). A few single-verb memory tools (recall, remember, forget, subscribe) deviate minimally but remain readable. No chaotic style mixing.

Tool Count2/5

34 tools is heavy and, more importantly, spans wildly different domains — a general Pipeworx data gateway, Polymarket betting analysis, AI-marketing visibility probes, memory/subscription plumbing, and a small ArcGIS Dublin GIS surface. Even allowing for a meta-gateway, the count sits firmly in the '25+' over-provisioned band and invites selection overload.

Completeness3/5

Coverage is broad but incoherent relative to the implied 'Arcgis Dublin' purpose — only search_datasets/layer_info/query_layer are GIS, and they are read-only with no layer create/update/delete. The gateway domain is well-covered (entity/profile/comparison/validation/memory/subscriptions), so the surface is functional but doesn't hang together as one coherent server.

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

Glama MCP Gateway

Add one secure layer between your agents and this server.