Skip to main content
Glama

Server Details

Prince William County GIS — Prince William County, 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
Uptime
42.4% over 41 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-arcgis-princewilliam
GitHub Stars
0
Server Listing
mcp-arcgis-princewilliam

TDQS

A3.9/5.0

Scored across 34 tools

Disambiguation3/5

Most tools have distinct, well-documented purposes, but there is genuine overlap: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical routers (the beta description admits it currently matches the stable version exactly), and six Polymarket tools (bet_research, polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread) require enormous descriptions to keep apart. The verbose descriptions do heavy lifting to disambiguate, but the routers and shared make selection fragile.

Naming Consistency4/5

Consistent snake_case throughout, with sensible namespace prefixes (ask_pipeworx_*, polymarket_*, pipeworx_*) that group related tools. Mixes verb_noun (resolve_entity, validate_claim) with noun_verb/noun_noun (ai_visibility_check, polymarket_arbitrage) but this stays readable and predictable.

Tool Count2/5

34 tools is heavy and far above the comfortable 3-15 range, and the breadth is jarring given the server is named for ArcGIS Prince William County — only three tools (search_datasets, layer_info, query_layer) are actually GIS, while the rest span SEC filings, Polymarket betting, LLM visibility probing, memory, and subscriptions. The count reflects a sprawling multi-product gateway rather than one coherent server.

Completeness4/5

Coverage is broad with few dead ends: the GIS surface (search→info→query) fully supports read-only access to open geospatial data, and the gateway offers complete lifecycles for memory (remember/recall/forget) and subscriptions (subscribe/list/unsubscribe/recent_alerts). Minor gaps only — no write/update operations anywhere and subscriptions lack an update, but these are outside the read-oriented scope.

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.