Skip to main content
Glama

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.

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

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds real behavioral value beyond that: geojson=true returns hazard shapes clipped to the suburb boundary in the same call, and the default false leaves the response unchanged.

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?

Two short paragraphs, purpose front-loaded in the first sentence, then the optional geojson behaviour and sibling routing. Little waste; the second paragraph's mention of separate calls is functional rather than filler.

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?

For a read-only, two-parameter bundle with no output schema, the description communicates what is returned (coverage share, risk band, distinct polygon count, optional clipped shapes) and what it excludes. The only gap is the undocumented suburb_name input, which no structured field covers.

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%: the geojson parameter is well documented in the schema, and the description reinforces it (clipping to boundary, returns coverage plus shapes). But suburb_name is undocumented in both schema and description — no format, naming convention or matching behaviour is given — so the description only partially compensates for the coverage gap.

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?

States a specific resource and scope: natural-hazard exposure for a suburb, specifically bushfire-prone area share and modelled flood overlay share, each with a risk band and polygon count. This clearly distinguishes it from siblings like suburbs_risks_slope, suburbs_risks_heritage_share and the single-hazard suburbs_risks_bushfire/flood tools.

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?

The description explicitly names the excluded hazard domains ('Slope, heritage, power lines and the per-property hazard counts are separate calls'), routing the agent away from this tool for those needs. However, it never says when to prefer this bundle over the individual suburbs_risks_bushfire / suburbs_risks_flood siblings, which is the most likely confusion.

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