Utah: Parcel Layer Info
utahparcels/get-layer-info
Returns the ArcGIS layer description for the Utah Statewide Parcels polygon layer of the State Geographic Information Database (SGID), about 1.6 million parcels: layer name, geometry type, maximum rows per query, every field with its type and alias, and the capabilities. Use it to see the columns behind the search tools; query-features searches PARCEL_ADD (site address), PARCEL_CITY, PARCEL_ZIP, PARCEL_ID, County or ACCOUNT_NUM. Field domain objects can make the answer large. Data from the State of Utah, SGID (Utah Geospatial Resource Center statewide parcels). Passed through unmodified and served by Eden Engine; not an official State of Utah product.
Price
$0.0026 per call
You pay the price shown. If a call turns out to cost more than its quote, you pay the actual price, capped at twice the quote. No monthly minimum. Top-ups start at $0.50.
Data source
Data from the State of Utah, SGID (Utah Geospatial Resource Center statewide parcels). Passed through unmodified and served by Eden Engine; not an official State of Utah product.
Use it
Five steps: search, inspect, learn, run, settle. No per-tool setup; your agent reaches this tool through the meta-tools it already has.
Connect once and your AI can find and run this tool, and any other it needs.
// 1. search: find the tool
omnial_search({ query: "what you need" })
// 2. inspect: price and input schema
omnial_inspect({ tool: "utahparcels/get-layer-info" })
// 3. learn: read the usage guide at runtime
omnial_learn({ tool: "utahparcels/get-layer-info" })
// 4. run: price the exact call first, then run it
omnial_execute({ tool: "utahparcels/get-layer-info", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "utahparcels/get-layer-info", input: { /* ... */ } })
// 5. settle: the call is charged when it finishes, nothing to doNot connected yet? Point your MCP client at https://mcp.eden-engine.com/mcp, then copy a config for your client.
Pricing
Every charge this tool can incur.
| Charge | Price |
|---|---|
Per call | $0.0026 |
- Updated
- Oct 25, 2026
Input and output schemas
Input schema
{
"type": "object",
"properties": {},
"additionalProperties": false
}Output schema
{
"type": "object",
"required": [
"name",
"fields"
],
"properties": {
"name": {
"type": "string"
},
"type": {
"type": "string"
},
"fields": {
"type": "array",
"items": {
"type": "object",
"required": [
"name",
"type"
],
"properties": {
"name": {
"type": "string"
},
"type": {
"type": "string"
},
"alias": {
"type": "string"
},
"length": {
"type": "integer"
}
},
"additionalProperties": true
},
"description": "Field definitions for the layer; a field `domain` object can be large."
},
"capabilities": {
"type": "string"
},
"displayField": {
"type": "string"
},
"geometryType": {
"type": "string"
},
"maxRecordCount": {
"type": "integer",
"description": "Most rows one upstream query returns."
}
},
"description": "The ArcGIS layer description: `name`, `type`, `geometryType`, `maxRecordCount`, `fields` (name, type, alias, length) and `capabilities`; the layer JSON carries many more keys, passed through as sent.",
"additionalProperties": true
}