Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Suburb · Recorded crime (Victoria)

suburbs_crime_recorded_offences_vic
Read-onlyIdempotent

Police-recorded offences in Victoria by suburb and by council area, per financial year (July to June) for 2016-17 to 2025-26, by offence type.

Coverage: Victoria: 2,880 suburbs and towns and 79 council areas; financial years 2016-17 to 2025-26. Current to 2026-06-30. Full description, field list and method: /v1/datasets/recorded-crime-vic.

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_vic"
  }
}

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, aggravated_robbery, assault_police_emergency_services_or_other_authorised_officer, begging, betting_and_gaming_offences, breach_bail_conditions, breach_family_violence_order, breach_intervention_order, breach_of_other_orders, cause_a_bushfire, cause_damage_by_fire, criminal_damage, criminal_intent, cruelty_to_animals, dangerous_driving, dangerous_substance_offences, defamation_and_libel, disorderly_conduct, drink_driving, drug_cultivation_and_manufacture, drug_dealing_and_trafficking, drug_driving, drug_use_and_possession, drunk_and_disorderly_in_public, environmental_offences, escape_custody, explosives_offences, fail_to_appear, family_violence_common_assault, family_violence_harassment_and_private_nuisance, family_violence_serious_assault, family_violence_stalking, family_violence_threatening_behaviour, fare_evasion, firearms_offences, forgery_false_information_bribery_and_other_deception, graffiti, hoaxes, improper_movement_on_public_or_private_space, licensing_offences, liquor_and_tobacco_licensing_offences, motor_vehicle_theft, neglect_or_ill_treatment_of_people, non_aggravated_robbery, non_family_violence_common_assault, non_family_violence_harassment_and_private_nuisance, non_family_violence_serious_assault, non_family_violence_stalking, non_family_violence_threatening_behaviour, non_residential_aggravated_burglary, non_residential_non_aggravated_burglary, obtain_benefit_by_deception, offensive_conduct, offensive_language, other_crimes_against_the_person, other_dangerous_or_negligent_acts_endangering_people, other_drug_offences, other_fire_related_offences, other_justice_procedures_offences, other_miscellaneous_offences, other_property_damage_offences, other_public_nuisance_offences, other_regulatory_driving_offences, other_regulatory_offences, other_theft, other_transport_regulation_offences, parking_offences, pervert_the_course_of_justice_or_commit_perjury, prison_regulation_offences, privacy_offences, prohibited_and_controlled_weapons_offences, public_health_and_safety_offences, public_security_offences, receiving_or_handling_stolen_goods, registration_and_roadworthiness_offences, residential_aggravated_burglary, residential_non_aggravated_burglary, resist_or_hinder_officer, riot_and_affray, steal_from_a_motor_vehicle, steal_from_a_retail_store, theft_of_a_bicycle, throw_or_discharge_object_endangering_people, unknown_aggravated_burglary, unknown_non_aggravated_burglary. Omit for all.
suburb_nameYesSuburb name exactly as /v1/suburbs/list returns it, e.g. `Bondi` or `St Kilda (Vic.)`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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, closed-world behavior, so the bar is lower. The description adds genuinely non-derivable context: 2,880 suburbs and 79 council areas, currency to 2026-06-30, the 2016-17 to 2025-26 window, and a 5¢ per-call cost — cost disclosure is especially valuable for agent budgeting. It does not discuss result size or pagination, but the cost and coverage disclosure compensates well.

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?

Front-loaded with what the data is, then coverage, then price — a sensible priority order. A few clauses are near-duplicative (the year range appears twice: in the first sentence and in the coverage paragraph), which costs a little tightness but nothing major.

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?

For a 4-parameter, no-output-schema read tool, the definition covers geography, granularity, temporal range, currency, cost, and points to a method/field-list endpoint. The remaining gap is that it never clarifies the suburb-vs-council-area relationship to the sibling lga tool, nor what the default response shape looks like when `fields` is omitted.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds meaning the schema does not: it establishes that `from`/`to` operate on a financial-year (July–June) axis rather than the quarterly/monthly formats the schema's examples suggest, and it implies `fields` values are offence types while the missing-field default returns everything. That is real interpretive value beyond the schema text.

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 resource (police-recorded offences), the geography (Victoria), the granularities (suburb and council area), and the time unit (financial year). It clearly differentiates the Victorian dataset from the sibling state datasets (_act, _nsw, _qld, _sa) by stating the jurisdiction explicitly. It stops short of distinguishing itself from `lga_crime_recorded_offences_vic`, which appears to overlap on council-area data.

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: an agent can infer it should call this for Victorian suburb-level crime and use the sibling state tools elsewhere. There is no explicit when-to-use/when-not statement, and no routing advice versus the lga_ variant despite the description claiming council-area coverage. The price note and docs pointer are helpful but are not selection guidance.

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