Microburbs Australian Property Data

Suburb · Crime

suburbs_crime_summary

Read-onlyIdempotent

Shown in the suburb report as the 'Crime' card in the Risks section.

Suburb and national total-crime medians (predicted incidents per 100,000 residents per year) with a vs-national verdict.

Price: 10¢ 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_crime_summary"
  }
}

Input Schema

Name	Required	Description	Default
`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": "Suburb vs national total-crime benchmark medians.",
-          "example": {
-            "area_level": "suburb",
-            "area_name": "Belmont North",
-            "national_median": 2787.6,
-            "suburb_median": 2248,
-            "unit": "predicted incidents per 100,000 residents per year",
-            "verdict": "Below average",
-            "vs_national_pct": -19
-          },
-          "properties": {
-            "area_level": {
-              "description": "Always 'suburb' for these endpoints.",
-              "title": "Area Level",
-              "type": "string"
-            },
-            "area_name": {
-              "description": "Suburb (SAL) name.",
-              "title": "Area Name",
-              "type": "string"
-            },
-            "national_median": {
-              "description": "Median total crime rate across all Australian mesh blocks, same unit as suburb_median.",
-              "title": "National Median",
-              "type": "number"
-            },
-            "suburb_median": {
-              "description": "Median total crime rate across this suburb's mesh blocks — predicted incidents per 100,000 residents per year (model trained on QLD Police 2020-2022 incident averages, predicted for all Australian mesh blocks).",
-              "title": "Suburb Median",
-              "type": "number"
-            },
-            "unit": {
-              "description": "Unit of suburb_median and national_median — always 'predicted incidents per 100,000 residents per year'.",
-              "title": "Unit",
-              "type": "string"
-            },
-            "verdict": {
-              "description": "Plain-English band for the delta: 'Very low', 'Below average', 'Average', 'Above average' or 'High'.",
-              "title": "Verdict",
-              "type": "string"
-            },
-            "vs_national_pct": {
-              "description": "Suburb median vs national median, as a rounded percentage delta (negative = less crime than the national median).",
-              "title": "Vs National Pct",
-              "type": "integer"
-            }
-          },
-          "required": [
-            "area_name",
-            "area_level",
-            "unit",
-            "suburb_median",
-            "national_median",
-            "vs_national_pct",
-            "verdict"
-          ],
-          "title": "CrimeSummary",
-          "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[CrimeSummary]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_CrimeSummary_"
-}New value: +null

First observedSep 14, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new operational context: a 10¢ per-call cost and the units of the returned figures. It does not state what happens for an unknown suburb or how missing data is represented, which keeps it short of a 5.

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

Conciseness5/5

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

Three short lines, zero filler, with the identity of the card front-loaded and the pricing isolated for easy scanning. The definition fits the tool's simplicity.

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?

With no output schema, the description carries the burden of describing return content, and it gestures at medians, national comparison, and units but not the actual field structure (e.g. suburb median, national median, verdict values). It also leaves the only parameter's format unaddressed, so an agent has enough to know what the tool yields but not enough to call it confidently.

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

Parameters2/5

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

Schema description coverage is 0% and there is a single required parameter, suburb_name, whose required format is never explained (bare name, name plus state, postcode, or an ID). The description does not compensate for the schema gap, leaving the agent to guess at a critical input.

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 names a specific data product: suburb and national total-crime medians in predicted incidents per 100,000 residents per year, plus a vs-national verdict. That is concrete and distinguishable from data-heavy siblings, though it never explicitly contrasts itself with suburbs_crime_breakdown or suburbs_crime_by_mesh_block.

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?

The mention that it appears as the 'Crime' card in the Risks section of the suburb report implies the intended use case (summary card data for a suburb report). There is no explicit when-to-use statement, no guidance on when the breakdown or mesh-block variants are more appropriate, and no prerequisite information about the required suburb_name value.

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?