Microburbs Australian Property Data

Suburb · Recorded crime (NSW)

suburbs_crime_recorded_offences_nsw

Read-onlyIdempotent

Police-recorded offences in New South Wales by suburb and by council area, per year for 2016-2025, by offence type.

Coverage: NSW: 4,479 suburbs and 129 council areas; calendar years 2016-2025. Current to 2025-12-31. Full description, field list and method: /v1/datasets/recorded-crime-nsw.

Price: 5¢ 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_recorded_offences_nsw"
  }
}

Input Schema

Name	Required	Description
`to`	No	Last period to include, same formats as `from`.
`from`	No	First period to include: 2020, 2020-Q3, 2020-07 or 2020-07-01.
`fields`	No	Comma-separated subset of: total_offences, abduction_and_kidnapping, arson, assault_police, attempted_murder, betting_and_gaming_offences, blackmail_and_extortion, breach_apprehended_violence_order, breach_bail_conditions, break_and_enter_dwelling, break_and_enter_non_dwelling, coercive_control, criminal_intent, cultivating_cannabis, dealing_trafficking_in_amphetamines, dealing_trafficking_in_cannabis, dealing_trafficking_in_cocaine, dealing_trafficking_in_ecstasy, dealing_trafficking_in_narcotics, dealing_trafficking_in_other_drugs, domestic_violence_related_assault, escape_custody, fail_to_appear, fraud, importing_drugs, intimidation_stalking_and_harassment, liquor_offences, malicious_damage_to_property, manslaughter, manufacture_drug, motor_vehicle_theft, murder, murder_accessory_conspiracy, non_domestic_violence_related_assault, offensive_conduct, offensive_language, other_drug_offences, other_offences, other_offences_against_justice_procedures, other_offences_against_the_person, other_theft, pornography_offences, possession_and_or_use_of_amphetamines, possession_and_or_use_of_cannabis, possession_and_or_use_of_cocaine, possession_and_or_use_of_ecstasy, possession_and_or_use_of_narcotics, possession_and_or_use_of_other_drugs, prohibited_and_regulated_weapons_offences, receiving_or_handling_stolen_goods, resist_or_hinder_officer, robbery_with_a_firearm, robbery_with_a_weapon_not_a_firearm, robbery_without_a_weapon, sexual_assault, sexual_touching_sexual_act_and_other_sexual_offences, steal_from_dwelling, steal_from_motor_vehicle, steal_from_person, steal_from_retail_store, stock_theft, transport_regulatory_offences, trespass. Omit for all.
`suburb_name`	Yes	Suburb name exactly as /v1/suburbs/list returns it, e.g. `Bondi` or `St Kilda (Vic.)`.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 13, 2026

TDQS

A3.6/5.0

Behavior4/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 safety is covered. The description adds genuinely non-obvious behavior: the 4,479-suburb / 129-council-area coverage, currency to 2025-12-31, and a per-call price of 5¢, which matters for an agent deciding whether to loop this call. It stops short of saying what a result row looks like or how rows are keyed.

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?

Purpose is front-loaded in the first sentence, followed by a compact coverage block and the price disclosure. Minor waste: the year range 2016-2025 appears twice (sentence one and the Coverage line), which could be collapsed.

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

Completeness5/5

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

Mis-set: a 4-parameter read-only tool with 100% schema coverage and no output schema needs little more than scope, currency and cost, all of which are present and accurate.

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 100%, so from/to/fields/suburb_name are already well documented in the schema, and the description adds no format details of its own. Its one contribution is pointing at `/v1/datasets/recorded-crime-nsw` for the field list and method, which is marginal since the schema already enumerates all offence fields. Baseline 3 applies.

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 specific resource ('Police-recorded offences in New South Wales') plus geography and time scope (suburb/council area, 2016-2025, by offence type), which is far beyond a restatement of the name. It does not explicitly contrast itself with the sibling lga_crime_recorded_offences_nsw, and the phrase 'by suburb and by council area' slightly muddies which geography this call keys on, given the only required parameter is suburb_name.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: nothing tells the agent to prefer this over the lga_* NSW tool, the other states' suburb crime tools, or the suburbs_crime_breakdown/summary siblings. The only contextual pointers are a dataset documentation path and the price line, neither of which is routing advice.

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?