Skip to main content
Glama

Server Details

Montana State GIS — Montana open geospatial data (ArcGIS).

The last two health checks of this connector failed. 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.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-arcgis-montana
GitHub Stars
0
Server Listing
mcp-arcgis-montana
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 47 tools

Disambiguation2/5

Several clusters have genuinely unclear boundaries: ask_pipeworx / ask_pipeworx_beta (which the description admits currently behaves identically) / ask_pipeworx_grounded / deep_research / validate_claim all answer natural-language questions, and the prediction-market cluster (polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, polymarket_edge_tracker, polymarket_kalshi_spread, bet_research, release_calendar_markets) overlaps heavily. The very long, cross-referencing descriptions ('PREFER OVER X', 'use Y instead') mitigate this somewhat, but they are effectively compensating for near-duplicate tools rather than describing distinct ones.

Naming Consistency3/5

Most names are snake_case, which is consistent, but the form is mixed: verb_noun (query_layer, resolve_entity, validate_claim, scan_dependency) alongside bare noun phrases (entity_profile, company_facts, prediction_calibration, polymarket_edges, archive_evidence, pipeworx_trending) and a suffix-variant triplet (ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded). It reads fine but there is no predictable pattern an agent can rely on to guess a name.

Tool Count2/5

47 tools is well past the heavy threshold, and the surface is a general-purpose data gateway rather than a scoped server. Against the stated 'Arcgis Montana' purpose, 44 of the 47 tools are unrelated to GIS, so the count is wildly disproportionate to the apparent domain.

Completeness2/5

For a GIS server the surface is thin: search_datasets, layer_info and query_layer are read-only — no spatial/geometry filtering beyond a SQL where clause, no geocoding, no dataset creation or editing, no basemap or raster handling. The bulk of the tools serve an unrelated finance/prediction-market/LLM-marketing domain, so the stated domain is severely under-served while the rest of the surface belongs to a different product entirely.

Tool Schema Changelog

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

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.