Microburbs Australian Property Data

Suburb · Hazard-overlay polygons by layer

suburbs_shapes_hazards

Read-onlyIdempotent

Hazard polygons for one layer, clipped to the suburb boundary (empty collection = hazard not present).

Price: 20¢ 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>",
      "layer": "<layer>"
    },
    "name": "suburbs_shapes_hazards"
  }
}

Input Schema

Name	Required	Description
`layer`	Yes	Hazard layer to return.
`geojson`	No	When false, geometry is dropped — every Feature keeps its `properties` but its `geometry` is null. Use it to fetch the counts and per-feature attributes without the coordinates (default true — response unchanged).
`suburb_name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 15, 2026

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": [
-        {
-          "additionalProperties": true,
-          "description": "Hazard-overlay polygons for one layer, clipped to the suburb.",
-          "example": {
-            "area_level": "suburb",
-            "area_name": "Belmont North",
-            "count": 36,
-            "geojson": {
-              "features": [
-                {
-                  "geometry": {
-                    "coordinates": [
-                      [
-                        [
-                          151.66,
-                          -32.99
-                        ],
-                        [
-                          151.67,
-                          -32.99
-                        ],
-                        [
-                          151.67,
-                          -33
-                        ],
-                        [
-                          151.66,
-                          -32.99
-                        ]
-                      ]
-                    ],
-                    "type": "Polygon"
-                  },
-                  "properties": {
-                    "category": "High Potential Bushfire Intensity"
-                  },
-                  "type": "Feature"
-                }
-              ],
-              "type": "FeatureCollection"
-            },
-            "layer": "bushfire"
-          },
-          "properties": {
-            "area_level": {
-              "const": "suburb",
-              "description": "Always 'suburb'.",
-              "title": "Area Level",
-              "type": "string"
-            },
-            "area_name": {
-              "description": "Canonical ABS SAL name.",
-              "title": "Area Name",
-              "type": "string"
-            },
-            "count": {
-              "description": "Number of hazard polygons returned (0 = none of this hazard here).",
-              "title": "Count",
-              "type": "integer"
-            },
-            "geojson": {
-              "additionalProperties": true,
-              "description": "GeoJSON FeatureCollection — hazard polygons clipped to the suburb boundary. Feature properties: `category` + `name` (per hazard layer), `tier` (acid-sulfate), none (landslide). Geometry is null on every Feature when the request passes `?geojson=false`.",
-              "title": "Geojson",
-              "type": "object"
-            },
-            "layer": {
-              "description": "The hazard layer requested.",
-              "enum": [
-                "bushfire",
-                "flood",
-                "heritage",
-                "erosion",
-                "landslide",
-                "acid-sulfate"
-              ],
-              "title": "Layer",
-              "type": "string"
-            }
-          },
-          "required": [
-            "area_name",
-            "area_level",
-            "layer",
-            "count",
-            "geojson"
-          ],
-          "title": "SuburbHazards",
-          "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[SuburbHazards]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_SuburbHazards_"
-}New value: +null

First observedSep 14, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds two genuinely useful behavioral facts: results are clipped to the suburb boundary and an empty collection means the hazard is absent, plus a per-call price. It still says nothing about coordinate reference system, feature volume, or whether suburb_name must match exactly.

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 sentences with zero filler; the empty-collection semantics and the price are the only content, and both earn their place. The price note is arguably a distraction mid-description but is still operationally relevant.

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

Completeness3/5

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

For a read-only polygon tool with no output schema, the description covers what a result means but leaves geometry format, CRS, and any feature limits unstated, and does not point to the mesh-block hazard alternative when suburb-level clipping is the wrong granularity.

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 67% and the geojson toggle is already thoroughly documented in the schema. The description adds meaning mainly for suburb_name by saying geometry is clipped to that boundary and for layer by saying only one is returned, but it adds no format details such as suburb name matching rules.

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

Purpose4/5

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

States a concrete resource and scope: hazard polygons for a single named layer, clipped to the suburb boundary. The clipping and single-layer framing implicitly separates it from mesh-block hazard siblings, but no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is only implied by 'for one layer' and by the empty-collection note, which tells the agent what a no-hazard result looks like. There is no explicit when-to-use versus the mesh-block or property-count hazard tools in the sibling set.

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 tools Inspect

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

Need Help?