Skip to main content
Glama

Server Details

Honolulu GIS — Honolulu, Hawaii 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
28.0% over 42 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-arcgis-honolulu
GitHub Stars
0
Server Listing
arcgis-honolulu

TDQS

A3.9/5.0

Scored across 34 tools

Disambiguation3/5

Most tools have clearly distinct purposes with richly documented boundaries, but there is real overlap: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research all describe a universal router (beta is documented as currently identical to stable), and the six polymarket_* tools plus bet_research form a dense cluster where an agent could easily misselect. The three GIS tools and the memory tools are clean and distinct.

Naming Consistency4/5

Nearly all names use consistent snake_case with descriptive verb_noun or noun_phrase forms (search_datasets, query_layer, entity_profile, validate_claim). Minor variance in style (ask_pipeworx vs deep_research) but no camelCase/snake_case mixing, so it reads predictably.

Tool Count2/5

34 tools is heavy and exceeds the comfortable range. The count is inflated by overlapping families — three ask_pipeworx variants, six polymarket tools, and a full memory/subscription/feedback layer — only three of which (search_datasets, layer_info, query_layer) relate to the advertised ArcGIS Honolulu purpose.

Completeness3/5

Against its name (Honolulu GIS), the surface is thin and read-only — search_datasets → layer_info → query_layer covers discovery and querying but offers no editing, geocoding, or analysis. Against the de facto domain (a general data gateway) coverage is broad, but the severe name/content mismatch makes the set feel incoherent rather than purpose-built.

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

Glama MCP Gateway

Add one secure layer between your agents and this server.