Tallahassee-Leon County GIS — Tallahassee-Leon County, Florida open geospatial data (ArcGIS).
Three well-named, read-only tools with complete input schemas and solid descriptions. All tools follow verb_noun naming (search_, query_, layer_info). Descriptions are clear and actionable (avg 180 chars), explaining WHAT each tool does and WHEN to use it. Input schemas are properly typed with required fields marked. However, output schemas are completely undocumented, LLMs cannot predict what fields to expect from responses. Parameter descriptions lack format constraints (e.g., 'limit: 1-50' is stated in description but not as JSON Schema bounds). No error handling guidance, raw HTTP errors are thrown without recovery hints. Missing tool annotations (readOnlyHint, idempotentHint) despite all three being read-only and idempotent. No pagination guidance in query_layer despite returning potentially large result sets.
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 Tallahassee-Leon County GIS open geospatial datasets (parcels, zoning, public works & planning) 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 completely undocumented. LLMs cannot predict response structure (fields, types, nesting). search_datasets returns {total, count, datasets[]} but this is invisible to the agent. query_layer and layer_info return raw ArcGIS JSON with no guidance on which fields matter.
No error handling guidance. Errors are thrown as raw HTTP status codes ('ArcGIS Hub: 404') without recovery hints. LLM cannot determine if error is retryable, user-fixable, or fatal. No guidance like 'Try a different org_id' or 'Check that the url is a valid Feature Service endpoint.'
Missing tool annotations. All three tools are read-only and idempotent, but lack readOnlyHint and idempotentHint annotations. This prevents agents from safely retrying on transient failures and understanding that these tools have no side effects.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 60 | 2026-07-28+ | v2 |
Parameter constraints stated in descriptions but not enforced in schema. 'limit: 1-50' and 'limit: 1-2000' are prose descriptions, not JSON Schema bounds (minimum/maximum). LLMs cannot parse prose constraints reliably and may pass invalid values.
query_layer lacks pagination guidance. No mention of how to handle large result sets, whether results are capped, or how to iterate. Returning 2000 features in one response could exhaust context window. Should document result limits and offer cursor/offset patterns.