Skip to main content
Glama

Server Details

Pima County GIS — Pima County, Arizona 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-pima
GitHub Stars
0
Server Listing
mcp-arcgis-pima
ChatGPT
–
Claude
–

TDQS

A3.9/5.0

Scored across 47 tools

Disambiguation3/5

Several clusters genuinely overlap: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research all route the same question (the beta is explicitly identical to the stable router today), polymarket_edges vs polymarket_arbitrage both surface opportunities, and entity_profile vs company_facts vs compare_entities vs recent_changes all answer 'tell me about company X'. The very long descriptions do a lot of work to separate these, but the agent must read paragraphs of caveats to pick correctly, and the duplicate beta router is a live misselection trap.

Naming Consistency4/5

Everything is consistently snake_case, and the family prefixes (ask_pipeworx*, polymarket_*, updown_*, archive_*, resolution_*) form readable groupings. The deviation is verb style: a mix of verb_noun (query_layer, search_datasets, validate_claim, resolve_entity) and bare noun_phrases (entity_profile, company_facts, deep_research, layer_info, recent_changes), which is a minor readability wrinkle rather than chaos.

Tool Count2/5

47 tools is heavy for any single MCP surface, and here the mismatch is severe: the server is named 'Arcgis Pima' but only 3 of 47 tools (search_datasets, layer_info, query_layer) touch Pima County GIS — the rest are Pipeworx platform tools spanning SEC data, prediction markets, LLM probing, memory, and subscriptions. The count only makes sense if this is an unsegmented everything-bundle, which imposes real selection cost on the agent.

Completeness3/5

For the nominal GIS domain the read chain is coherent (search_datasets → layer_info → query_layer) and read-only is appropriate for open data, but it stops at attribute queries: no geocoding/address lookup, no spatial/geometry filter or proximity query, no service- or layer-listing for a known service URL, and no export. The broader platform surface is vast yet uneven (deep research and subscriptions gated behind accounts), so coverage is broad but not a clean lifecycle anywhere.

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.