Microburbs Australian Property Data

by au.com.microburbs

Overview Discussions Admin

Suburb · Noise level

suburbs_shapes_noise_heatmap

Read-onlyIdempotent

Shown in the suburb report as the 'Noise level' map layer (the 'Noise' card) in the Risks section.

Precomputed noise colour regions clipped to the suburb, plus cell-centre heat points.

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>"
    },
    "name": "suburbs_shapes_noise_heatmap"
  }
}

Input Schema

Name	Required	Description	Default
`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": "Noise-map colour regions clipped to the suburb boundary.",
-          "example": {
-            "area_level": "suburb",
-            "area_name": "Belmont North",
-            "count": 6,
-            "geojson": {
-              "features": [
-                {
-                  "geometry": {
-                    "coordinates": [
-                      [
-                        [
-                          151.66,
-                          -32.99
-                        ],
-                        [
-                          151.67,
-                          -32.99
-                        ],
-                        [
-                          151.67,
-                          -33
-                        ],
-                        [
-                          151.66,
-                          -32.99
-                        ]
-                      ]
-                    ],
-                    "type": "Polygon"
-                  },
-                  "properties": {
-                    "color": "#990000",
-                    "fill_opacity": 0.7
-                  },
-                  "type": "Feature"
-                }
-              ],
-              "type": "FeatureCollection"
-            },
-            "heat": [
-              [
-                -32.9931,
-                151.6688,
-                0.8
-              ]
-            ],
-            "intensity_definition": "Relative noise intensity, 0-1 (scaled composite of road-traffic and noisy-POI proximity; 1 = noisiest cell in the source grid). Not a decibel measurement."
-          },
-          "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 colour-region features returned.",
-              "title": "Count",
-              "type": "integer"
-            },
-            "geojson": {
-              "additionalProperties": true,
-              "description": "GeoJSON FeatureCollection — precomputed noise colour regions clipped to the suburb polygon. Feature properties are render-ready styling: `color` (hex fill) and `fill_opacity`; the numeric intensity values live in `heat`. Geometry is null on every Feature when the request passes `?geojson=false`.",
-              "title": "Geojson",
-              "type": "object"
-            },
-            "heat": {
-              "description": "Cell-centre points inside the suburb as `[lat, lng, intensity]` triples, ready for heatmap-style rendering. `intensity` is the relative 0-1 noise score described by intensity_definition.",
-              "items": {
-                "items": {
-                  "type": "number"
-                },
-                "type": "array"
-              },
-              "title": "Heat",
-              "type": "array"
-            },
-            "intensity_definition": {
-              "description": "What the intensity numbers mean — a relative 0-1 noise score (composite road-traffic + noisy-POI proximity), not decibels.",
-              "title": "Intensity Definition",
-              "type": "string"
-            }
-          },
-          "required": [
-            "area_name",
-            "area_level",
-            "count",
-            "intensity_definition",
-            "geojson",
-            "heat"
-          ],
-          "title": "SuburbNoiseHeatmap",
-          "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[SuburbNoiseHeatmap]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_SuburbNoiseHeatmap_"
-}New value: +null

First observedSep 14, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds genuinely useful non-schema context: the 20¢ per-call cost and the output composition (colour regions plus heat points), but says nothing about response size, coordinate system, or precision.

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?

Three short, front-loaded blocks with no filler; the report-card context comes first, the output shape second, and cost last. The only marginal line is the UI cross-reference to the 'Noise' card, which serves as locational context rather than tool selection guidance.

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 only two parameters, no output schema, and simple annotations, the description covers what an agent needs: what the data is, what features it returns, the clipping scope, and the price. Nothing critical is missing for correct invocation, though the absence of any aircraft-noise differentiation leaves a sibling-selection ambiguity.

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 description coverage is 50%: geojson is thoroughly documented in the schema itself, while suburb_name has no description anywhere. The description adds no parameter meaning beyond the schema, though suburb_name is largely self-explanatory, keeping this at an adequate baseline rather than penalizing it.

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?

The description gives a concrete verb-and-resource: precomputed noise colour regions clipped to a suburb plus cell-centre heat points, and anchors it to the 'Noise level' layer in the suburb report. It does not, however, distinguish itself from the aircraft-noise siblings (suburbs_environment_aircraft_noise, suburbs_mesh_blocks_aircraft_noise), so the agent must infer which noise source this covers.

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?

There is no explicit when-to-use or when-not-to-use statement, and no alternative tool is named. The 'Noise level map layer in the suburb report' framing implies the usage context (fetching a mapped noise layer for a suburb) but leaves the reader to infer it.

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?