Skip to main content
Glama

Arcgis Stanislaus

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Stanislaus County GIS — Stanislaus County, California 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
0.4% over 24 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-arcgis-stanislaus
GitHub Stars
0
Server Listing
arcgis-stanislaus

TDQS

A3.8/5.0

Scored across 39 tools

Disambiguation3/5

Many tools are distinct, but the research/query entry points overlap heavily (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, suggest_questions), and several Polymarket scanners (bet_research, polymarket_arbitrage, polymarket_edges) require careful reading to choose correctly. Descriptions provide guidance, so boundaries are not chaotic, but multiple tools have unclear edges for an agent.

Naming Consistency4/5

Tool names are consistently snake_case throughout, with predictable prefixes for Pipeworx, Polymarket, and Kalshi families. Some names are verb_noun while others are noun phrases (entity_profile, company_facts, layer_info), so the convention is mostly but not perfectly consistent.

Tool Count2/5

39 tools is a heavy surface for a single server, exceeding the typical 3-15 well-scoped range. The mismatch is especially stark because the server is named Arcgis Stanislaus but only three tools are GIS-related; the rest are a broad Pipeworx/Prediction-market toolkit.

Completeness3/5

The Pipeworx meta-surface is broad, covering research, company facts, prediction markets, memory, subscriptions, and some AI visibility workflows. However, the ArcGIS Stanislaus domain is limited to discovery, schema, and query with no richer geospatial operations or editing lifecycle, and several domains rely on the router rather than explicit tools.

Tool Schema Changelog

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

  1. 1 tool update
    • Changedrelease_calendar_markets2 fields changed
      • addedOutput schema / properties / empty_reason
        Added value: +{
+  "description": "Present ONLY on a zero-release window: \"no_releases_in_window\". The window was queried and nothing is scheduled — this is an answer, not a failure.",
+  "type": "string"
+}
      • addedOutput schema / properties / hint
        Added value: +{
+  "description": "Present ONLY on a zero-release window: what to change (usually a wider `hours`).",
+  "type": "string"
+}
  2. 39 tool updates
    • First observedai_visibility_check
    • First observedask_pipeworx
    • First observedask_pipeworx_beta
    • First observedask_pipeworx_grounded
    • First observedbet_research
    • First observedcompany_facts
    • First observedcompare_entities
    • First observeddeep_research
    • First observeddiscover_tools
    • First observedentity_profile
    • First observedforget
    • First observedgenerate_llms_txt
    • First observedkalshi_weather_edge
    • First observedlayer_info
    • First observedlist_subscriptions
    • First observedpipeworx_feedback
    • First observedpipeworx_trending
    • First observedpolymarket_arbitrage
    • First observedpolymarket_edge_tracker
    • First observedpolymarket_edges
    • First observedpolymarket_fill_risk
    • First observedpolymarket_kalshi_spread
    • First observedquery_layer
    • First observedrecall
    • First observedrecent_alerts
    • First observedrecent_changes
    • First observedrelease_calendar_markets
    • First observedremember
    • First observedresolution_audit
    • First observedresolution_diff
    • First observedresolve_entity
    • First observedscan_competitor_ai_presence
    • First observedscan_dependency
    • First observedsearch_datasets
    • First observedsearch_within
    • First observedsubscribe
    • First observedsuggest_questions
    • First observedunsubscribe
    • First observedvalidate_claim

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