Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Suburb · Bushfire + flood — bundle

suburbs_risks_all
Read-onlyIdempotent

Natural-hazard exposure for the suburb: how much of its area sits inside a designated bushfire-prone area and inside a modelled flood overlay, each with a plain risk band and the number of distinct hazard polygons.

Pass geojson=true to get the hazard shapes themselves, clipped to the suburb boundary, in the same call. Slope, heritage, power lines and the per-property hazard counts are separate calls.

Price: 11¢ per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "suburb_name": "<suburb_name>"
    },
    "name": "suburbs_risks_all"
  }
}

Input Schema

NameRequiredDescriptionDefault
geojsonNoWhen true, each sub-risk additionally carries a `geojson` FeatureCollection clipped to the suburb boundary — one call returns coverage plus every risk shape (default false — response unchanged).
suburb_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "available": {
-      "anyOf": [
-        {
-          "type": "boolean"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "`false` on no-data responses. Omitted on success — branch on `data !== null` if you want a single discriminator.",
-      "title": "Available"
-    },
-    "data": {
-      "anyOf": [
-        {
-          "properties": {
-            "bushfire": {
-              "anyOf": [
-                {
-                  "additionalProperties": true,
-                  "description": "One suburb-level risk record (bushfire or flood).\n\n`coverage_pct` is the share of the SAL covered by the modelled\nrisk overlay. `risk_band` is a coarse low/moderate/high band — only\npopulated for flood today; bushfire reports the raw percentage.",
-                  "example": {
-                    "area_level": "suburb",
-                    "area_name": "Belmont North",
-                    "coverage_pct": 45.72,
-                    "name": "Bushfire",
-                    "value_unit": "% of suburb area"
-                  },
-                  "properties": {
-                    "area_level": {
-                      "description": "Always 'suburb'.",
-                      "title": "Area Level",
-                      "type": "string"
-                    },
-                    "area_name": {
-                      "description": "Suburb (SAL) name.",
-                      "title": "Area Name",
-                      "type": "string"
-                    },
-                    "coverage_pct": {
-                      "description": "Share of suburb area inside the overlay (%).",
-                      "title": "Coverage Pct",
-                      "type": "number"
-                    },
-                    "geojson": {
-                      "anyOf": [
-                        {
-                          "additionalProperties": true,
-                          "type": "object"
-                        },
-                        {
-                          "type": "null"
-                        }
-                      ],
-                      "description": "GeoJSON FeatureCollection of the hazard polygons for this layer, ST_Intersection-clipped to the suburb boundary and simplified for browser use. Present only when the request passes `?geojson=true`; absent (and the response byte-identical to before) otherwise.",
-                      "title": "Geojson"
-                    },
-                    "geojson_meta": {
-                      "anyOf": [
-                        {
-                          "additionalProperties": true,
-                          "type": "object"
-                        },
-                        {
-                          "type": "null"
-                        }
-                      ],
-                      "description": "Clip / simplify / truncation metadata for `geojson` (clip method, simplify tolerance, coordinate precision, feature cap, and whether the size cap truncated the output). Present only with `?geojson=true`.",
-                      "title": "Geojson Meta"
-                    },
-                    "name": {
-                      "description": "Risk overlay name — 'Bushfire' or 'Flood'.",
-                      "title": "Name",
-                      "type": "string"
-                    },
-                    "risk_band": {
-                      "anyOf": [
-                        {
-                          "type": "string"
-                        },
-                        {
-                          "type": "null"
-                        }
-                      ],
-                      "description": "Coarse band — 'low' / 'moderate' / 'high'. Currently flood only.",
-                      "title": "Risk Band"
-                    },
-                    "value_unit": {
-                      "description": "Unit for coverage_pct — '% of suburb area'.",
-                      "title": "Value Unit",
-                      "type": "string"
-                    }
-                  },
-                  "required": [
-                    "area_name",
-                    "area_level",
-                    "name",
-                    "coverage_pct",
-                    "value_unit"
-                  ],
-                  "title": "SuburbRisk",
-                  "type": "object"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "example": {
-                "area_level": "suburb",
-                "area_name": "Belmont North",
-                "coverage_pct": 45.72,
-                "name": "Bushfire",
-                "value_unit": "% of suburb area"
-              }
-            },
-            "flood": {
-              "anyOf": [
-                {
-                  "additionalProperties": true,
-                  "description": "One suburb-level risk record (bushfire or flood).\n\n`coverage_pct` is the share of the SAL covered by the modelled\nrisk overlay. `risk_band` is a coarse low/moderate/high band — only\npopulated for flood today; bushfire reports the raw percentage.",
-                  "example": {
-                    "area_level": "suburb",
-                    "area_name": "Belmont North",
-                    "coverage_pct": 45.72,
-                    "name": "Bushfire",
-                    "value_unit": "% of suburb area"
-                  },
-                  "properties": {
-                    "area_level": {
-                      "description": "Always 'suburb'.",
-                      "title": "Area Level",
-                      "type": "string"
-                    },
-                    "area_name": {
-                      "description": "Suburb (SAL) name.",
-                      "title": "Area Name",
-                      "type": "string"
-                    },
-                    "coverage_pct": {
-                      "description": "Share of suburb area inside the overlay (%).",
-                      "title": "Coverage Pct",
-                      "type": "number"
-                    },
-                    "geojson": {
-                      "anyOf": [
-                        {
-                          "additionalProperties": true,
-                          "type": "object"
-                        },
-                        {
-                          "type": "null"
-                        }
-                      ],
-                      "description": "GeoJSON FeatureCollection of the hazard polygons for this layer, ST_Intersection-clipped to the suburb boundary and simplified for browser use. Present only when the request passes `?geojson=true`; absent (and the response byte-identical to before) otherwise.",
-                      "title": "Geojson"
-                    },
-                    "geojson_meta": {
-                      "anyOf": [
-                        {
-                          "additionalProperties": true,
-                          "type": "object"
-                        },
-                        {
-                          "type": "null"
-                        }
-                      ],
-                      "description": "Clip / simplify / truncation metadata for `geojson` (clip method, simplify tolerance, coordinate precision, feature cap, and whether the size cap truncated the output). Present only with `?geojson=true`.",
-                      "title": "Geojson Meta"
-                    },
-                    "name": {
-                      "description": "Risk overlay name — 'Bushfire' or 'Flood'.",
-                      "title": "Name",
-                      "type": "string"
-                    },
-                    "risk_band": {
-                      "anyOf": [
-                        {
-                          "type": "string"
-                        },
-                        {
-                          "type": "null"
-                        }
-                      ],
-                      "description": "Coarse band — 'low' / 'moderate' / 'high'. Currently flood only.",
-                      "title": "Risk Band"
-                    },
-                    "value_unit": {
-                      "description": "Unit for coverage_pct — '% of suburb area'.",
-                      "title": "Value Unit",
-                      "type": "string"
-                    }
-                  },
-                  "required": [
-                    "area_name",
-                    "area_level",
-                    "name",
-                    "coverage_pct",
-                    "value_unit"
-                  ],
-                  "title": "SuburbRisk",
-                  "type": "object"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "example": {
-                "area_level": "suburb",
-                "area_name": "Belmont North",
-                "coverage_pct": 7.2,
-                "name": "Flood",
-                "risk_band": "moderate",
-                "value_unit": "% of suburb area"
-              }
-            }
-          },
-          "title": "SuburbRisksAll",
-          "type": "object"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "The endpoint's payload, or `null` when Microburbs has no value."
-    },
-    "message": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "Human-readable explanation. Omitted on success.",
-      "title": "Message"
-    },
-    "reason": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "Machine-readable slug naming the no-data condition (e.g. `no_avm_for_GANSW704074813`). Stable per endpoint. Omitted on success.",
-      "title": "Reason"
-    }
-  },
-  "title": "ApiResponse[SuburbRisksAll]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_SuburbRisksAll_"
-}New value: +null
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds two genuinely useful traits beyond that: per-call cost (11¢) and the fact that geojson=true expands the payload with boundary-clipped shapes while the default response is unchanged. It says nothing about failure behavior for unknown or ambiguous suburb names, which matters for a lookup keyed on a free-text name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the substantive answer (coverage, band, polygon counts) before the optional parameter and the cost, so an agent can triage quickly. Slight redundancy in describing geojson's clipping twice (prose and schema), but no padding sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-value burden and does it: area shares, plain risk bands, and distinct polygon counts are all named. The remaining gap is the required suburb_name's expected format and resolution behavior, the one thing an agent could get wrong before calling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: geojson is fully documented in the schema and the description merely restates its clipping behavior, while suburb_name has no schema description and the prose gives no format guidance (state, postcode, or disambiguation for duplicate names). Baseline 3 is right — the description neither harms nor compensates for the undocumented required parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource and scope: bushfire-prone-area share and modelled flood-overlay share for a suburb, each with a risk band and hazard-polygon count. It also explicitly separates itself from the per-property hazard tools and the single-layer risk tools (slope, heritage, power lines), so an agent can place it without opening siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context for use and explicitly tells the agent that slope, heritage, power lines and per-property hazard counts are separate calls, which routes it away from this tool. It never states the inverse case (when to call suburbs_risks_bushfire and suburbs_risks_flood separately instead of this bundle), so cost-driven selection is only implied by the stated 11¢ price.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Microburbs Australian Property Data toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources