Skip to main content
Glama

Arcgis Glynncounty

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Glynn County GIS — Glynn County, Georgia 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
24.6% over 47 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-arcgis-glynncounty
GitHub Stars
0
Server Listing
arcgis-glynncounty

TDQS

A3.7/5.0

Scored across 34 tools

Disambiguation2/5

Heavy overlaps: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded are near-identical routers (beta even states it matches the stable one), and polymarket_edges / polymarket_arbitrage / polymarket_edge_tracker / polymarket_fill_risk all cover prediction-market analysis. discover_tools vs suggest_questions and entity_profile vs recent_changes vs compare_entities also blur together, making misselection likely.

Naming Consistency3/5

Everything is snake_case, which is consistent, but the convention is mixed: verb_phrases (ask_pipeworx, resolve_entity, validate_claim), noun_phrases (entity_profile, recent_changes, layer_info), and family prefixes (polymarket_*, pipeworx_*). It is readable but not a single predictable pattern.

Tool Count2/5

34 tools is heavy for a single server, and the count is inflated by redundant members (a beta duplicate router, several overlapping polymarket tools). A tighter set would serve the same purposes without the ambiguity.

Completeness3/5

The surface is broad across QA, entity resolution, comparison, monitoring, and memory, but the GIS domain implied by the server name is thinly covered — only search_datasets, query_layer, and layer_info, with no create/update/delete operations. Notable gaps remain relative to the apparent geospatial scope.

Tool Schema Changelog

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

  1. 1 tool update
    • Changedentity_profile3 fields changed
      • changedInput schema / properties / type / description
        Previous value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon."
      • changedInput schema / properties / type / enum
        Previous value: -[
-  "company"
-]New value: +[
+  "company",
+  "ticker"
+]
      • changedInput schema / properties / value / description
        Previous value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."
  2. 1 tool update
    • Changedresolve_entity1 field changed
      • changedInput schema / properties / value / description
        Previous value: -"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\")."New value: +"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\"). Pass the ENTITY NAME ONLY — for a bond that is the ISSUER exactly as printed (\"NEW YORK ST DORM AUTH\"), never the question's full noun phrase (\"NEW YORK ST DORM AUTH revenue bonds\"): the FIGI lookup matches instrument names, so trailing security-class words match nothing."

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