Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

LGA · Recorded crime (NSW)

lga_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": {
      "lga_name": "<lga_name>"
    },
    "name": "lga_crime_recorded_offences_nsw"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast period to include, same formats as `from`.
fromNoFirst period to include: 2020, 2020-Q3, 2020-07 or 2020-07-01.
fieldsNoComma-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.
lga_nameYesCouncil (LGA) name exactly as /v1/lga/list returns it, e.g. `Lake Macquarie`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive and closed-world behaviour, so the description's job is to add context and it does: coverage counts (4,479 suburbs / 129 LGAs), currency to 2025-12-31, and a per-call price of 5¢ which materially affects an agent's decision to call. It stops short of describing pagination, row limits, or result shape, so it is not 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.

Conciseness4/5

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

Three short paragraphs with the resource statement front-loaded, followed by coverage limits, then pricing. Minimal waste, though the 'by suburb and by council area' clause adds ambiguity rather than information for an LGA-only tool.

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 should say something about the shape of the returned rows (e.g. one record per LGA-year with the selected offence columns), yet it does not, and it also omits any row-limit or pagination note. Coverage, currency and pricing are well covered, and the docs pointer partially offloads the rest.

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% and every parameter (from, to, fields, lga_name) is documented there, including the accepted date formats and the full field list. The description adds no extra parameter meaning, so the 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?

Names a specific resource (police-recorded offences), a jurisdiction (New South Wales), a granularity (council area / LGA), a time range (2016-2025) and a dimension (offence type). The one weak spot is the phrase 'by suburb and by council area', which suggests suburb-level output even though this tool requires an lga_name and a suburb-level sibling exists, so the boundary with suburbs_crime_recorded_offences_nsw is not drawn.

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 implied rather than stated: the reader infers 'query LGA-level crime counts here'. There is no explicit when-to-use, when-not-to-use, or pointer to the suburb/QLD/VIC siblings, only a docs pointer to /v1/datasets/recorded-crime-nsw.

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