Skip to main content
Glama

Server Details

City of Toledo GIS — Toledo, Ohio 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-toledo
GitHub Stars
0
Server Listing
mcp-arcgis-toledo
ChatGPT
–
Claude
–

TDQS

A3.8/5.0

Scored across 47 tools

Disambiguation2/5

Several clusters are functionally indistinguishable: ask_pipeworx, ask_pipeworx_beta (self-described as identical to ask_pipeworx) and ask_pipeworx_grounded all route the same question, and deep_research/discover_tools/suggest_questions all serve 'what tools exist / what can I ask'. Prediction-market coverage is similarly crowded — polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, polymarket_fill_risk, release_calendar_markets and bet_research overlap heavily, and the descriptions work so hard to differentiate themselves that selection is still guesswork. Only the ArcGIS trio (search_datasets, layer_info, query_layer) and the entity/financial tools draw clean lines.

Naming Consistency4/5

Every name is snake_case with no camelCase or casing drift, and there are recognizable prefix families (polymarket_*, archive_*, updown_*, ask_pipeworx*). The verb style is not uniform — verb_noun (query_layer, compare_entities, validate_claim) mixes with bare nouns (company_facts, entity_profile, resolution_audit) and single-word verbs (remember, forget, recall, subscribe) — but the result stays readable and predictable.

Tool Count2/5

47 tools is well past the point where an agent can hold the surface in mind, and the count is inflated by redundancy rather than scope: three ask_pipeworx variants, six-plus Polymarket tools, several overlapping entity-lookup tools. A server actually scoped to Toledo GIS needs a handful of tools, not 47.

Completeness2/5

For the stated 'Arcgis Toledo' domain the surface is only search_datasets, layer_info and query_layer — read-only layer access with no feature create/update/delete, no geocoding, no spatial filter or map export, so any write or analysis workflow dead-ends. The bulk of the toolset belongs to an unrelated Pipeworx data/prediction-market platform, which leaves the advertised GIS purpose severely under-covered.

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.