The GIS toolset
The esri, open-data, and postgis tools in the configuration.
The GIS toolset registers three tools the agent can call:
| Tool | Key calls | Talks to |
|---|---|---|
esri | query_features, geocode_address, search_portal_items | ArcGIS Online / Enterprise |
open-data | search, fetch | Public portals (ArcGIS Hub, Socrata, data.gov) |
postgis | run_readonly_sql, describe_layer | Your PostGIS database |
The Esri tool wraps the Esri MCP, which exposes search_portal_items,
get_item_details, list_layers, get_layer_info, query_features,
geocode_address, and reverse_geocode.
Enabling and toggling
hermes tools
# [x] esri
# [x] open-data
# [ ] postgis <- toggle per toolConfiguration
The tools read credentials from the environment at call time; the agent never passes raw secrets to the model.
ARCGIS_TOKEN=...
POSTGIS_URL=postgresql://user:pass@host:5432/gis_labThe esri tool uses your existing ArcGIS token flow, so it respects the
same authentication and item permissions your team already has.
Least privilege
Give postgis a read-only role. The agent should be able to query your
parcels, not rewrite them.
Open data
The open-data tool searches public data portals by bounding box and
keywords, so the agent can find and pull published datasets without a
per-portal integration. Census enrichment is available through the Census
MCP alongside it.
Adding your own tools
Because these are ordinary Hermes tools, anything you write for the Hermes toolset system works alongside them. The GIS toolset is not special; it is just the one this configuration maintains.