Skip to main content
Glama

Server Details

City of Onkaparinga GIS — Onkaparinga, South Australia 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-onkaparinga
GitHub Stars
0
Server Listing
mcp-arcgis-onkaparinga
ChatGPT
–
Claude
–

TDQS

A3.6/5.0

Scored across 47 tools

Disambiguation2/5

Several clusters have genuinely fuzzy boundaries: ask_pipeworx, ask_pipeworx_beta (documented as currently identical), ask_pipeworx_grounded and deep_research all answer questions from the same catalog, differing only in grounding/depth. The prediction-market surface is even denser — polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, bet_research, polymarket_fill_risk and polymarket_kalshi_spread overlap on 'find/size an edge', and entity_profile vs company_facts vs compare_entities vs recent_changes require careful reading to separate.

Naming Consistency3/5

Most names are snake_case and readable, but conventions are mixed: verb_noun (resolve_entity, query_layer, compare_entities) alongside bare noun phrases (entity_profile, company_facts, layer_info, prediction_calibration) and a `pipeworx`/`_beta` naming layer that adds no predictable signal. The GIS tools follow the verb_noun pattern; the meta/research tools do not.

Tool Count1/5

47 tools on a server named for a single city's ArcGIS instance is an extreme mismatch — only search_datasets, layer_info and query_layer have anything to do with Onkaparinga GIS. The remaining ~44 tools are a generic multi-domain data platform (SEC/EDGAR, FRED, prediction markets, LLM visibility audits, memory, subscriptions), so the surface is far beyond the apparent scope and hard to hold in context.

Completeness2/5

For the stated GIS domain the surface is read-only and thin: discovery, schema and attribute queries exist, but no spatial/geometry predicates, no feature editing or export, no map/image or metadata-management operations. The generic-data half is broad but has visible holes (PatentsView sunset soft-fails, no PyPI/Maven dependency coverage, subscriptions require OAuth), so neither purpose is fully closed out.

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.