City of Henderson GIS — Henderson, Nevada open geospatial data (ArcGIS). Provides access to parcels, zoning, public works & city services datasets through ArcGIS Feature Services.
Three well-named, read-only tools with complete input schemas and clear descriptions. All tools follow verb_noun naming (search_*, query_*, layer_info). Descriptions are substantive (120 - 180 chars) and explain what each tool does and when to use it. Input schemas include type definitions and parameter descriptions. However, output schemas are not documented, LLMs cannot predict what fields to expect from responses. Parameter descriptions lack explicit constraints (e.g., 'limit: 1-50' is stated in description but not formalized). No error handling guidance or recovery hints. Security is solid (SSRF guard in layerUrl, no secrets exposed), but error messages are generic ('ArcGIS query: 404') rather than actionable.
Get an ArcGIS Feature/Map Service layer's schema by url: fields (name + type), geometry type, total record count, and capabilities.
Query an ArcGIS Feature Service / Map Service layer by its url (from search_datasets). SQL-like `where`, comma-separated `out_fields`, `order_by`, `limit`, `offset`. Returns attribute rows (and geometry). Use where="1=1" + out_fields="*" to sample.
Search City of Henderson GIS open geospatial datasets (parcels, zoning, public works & city services) by keyword. Returns each dataset's name, summary, record_count, owner/org, and its Feature Service `url` — pass that url to query_layer / layer_info.
Output schemas not documented. LLMs cannot predict response structure (fields, types, pagination). Forces agents to guess or fail on unexpected formats.
Error messages are generic ('ArcGIS query: 404') and do not guide recovery. LLMs cannot determine if the error is retryable, user-fixable, or fatal.
Parameter constraints (e.g., limit 1-50, 1-2000) are stated in descriptions but not formalized as JSON Schema min/max. LLMs may pass out-of-range values.
query_layer and layer_info accept arbitrary ArcGIS URLs. While layerUrl() validates HTTPS and path format, no rate limiting or timeout handling is visible. Runaway agents could hammer external services.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 61 | 2026-07-28+ | v2 |
No pagination guidance in search_datasets response. If total > 50, LLM cannot fetch remaining results. Response should include next_cursor or total_count.