City of Abbotsford GIS — Abbotsford, BC (Canada) open geospatial data (ArcGIS). Provides access to parcels, zoning, public works & city services datasets via ArcGIS Feature Service queries.
Three well-named, read-only tools with clear descriptions and complete input schemas. All tools follow verb_noun naming (search_*, query_*, layer_info). Descriptions are 150 - 250 chars, within the 10 - 1024 baseline. All parameters have type definitions and descriptions. However, output schemas are not documented, LLMs cannot predict response structure for downstream planning. Error handling is minimal (generic HTTP status errors). No parameter constraints (enums, ranges) despite opportunities (e.g., limit 1 - 50 for search_datasets, 1 - 2000 for query_layer). SSRF guard in layerUrl() is a security plus. Missing: output schema documentation, enum constraints, error recovery guidance.
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 Abbotsford 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, nesting) for downstream tool calls or data extraction. search_datasets returns {total, count, datasets[{id, name, summary, org, org_id, record_count, type, url}]} but this is inferred from code, not declared in tool definition.
No enum constraints on parameters with known valid ranges. limit (1 - 50 for search_datasets, 1 - 2000 for query_layer) and where/out_fields accept free-form strings, inviting invalid SQL or field names. LLMs cannot self-correct without explicit constraints.
Error responses are generic HTTP status codes (e.g., 'ArcGIS Hub: 401', 'ArcGIS query: 500'). No recovery guidance. LLM cannot determine if error is retryable, user-fixable, or fatal. Missing: categorized errors with actionable next steps.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 61 | 2026-07-28+ | v2 |
Parameter descriptions include example values ('e.g. "parcels", "crime", "flood zones"' for query; 'e.g. "STATE = \'CA\' AND YEAR >= 2020"' for where). LLMs tend to reuse examples literally rather than adapt to context, causing failures.
No pagination guidance in query_layer description. Tool accepts limit (1 - 2000) and offset but does not explain how to iterate large result sets or when to use pagination. LLMs may request all 2000 records in one call, exhausting context.