Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

LGA · Recorded crime (Queensland)

lga_crime_recorded_offences_qld
Read-onlyIdempotent

Police-recorded offences in Queensland by council area, per year for 2016-2025, by offence type.

Coverage: Queensland: 77 council areas; calendar years 2016-2025. Current to 2025-12-31. Full description, field list and method: /v1/datasets/recorded-crime-qld.

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

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, advertising_prostitution, armed_robbery, arson, attempted_murder, bomb_possess_and_or_use_of, breach_domestic_violence_protection_order, coercive_control, common_assault, conspiracy_to_murder, dangerous_operation_of_a_vehicle, disobey_move_on_direction, disqualified_driving, drink_driving, driving_causing_death, extortion, fare_evasion, found_in_places_used_for_purpose_of_prostitution_offences, fraud_by_cheque, fraud_by_computer, fraud_by_credit_card, gaming_racing_and_betting_offences, grievous_assault, have_interest_in_premises_used_for_prostitution_offences, homicide_murder, identity_fraud, interfere_with_mechanism_of_motor_vehicle, kidnapping_and_abduction_etc, knowingly_participate_in_provision_prostitution_offences, life_endangering_acts, liquor_excl_drunkenness, manslaughter_excl_by_driving, manslaughter_unlawful_striking_causing_death, miscellaneous_offences, other_drug_offences, other_fraud, other_handling_stolen_goods, other_property_damage, other_prostitution_offences, other_sexual_offences, other_stealing, permit_minor_to_be_at_a_place_used_for_prostitution_offences, possess_and_or_use_other_weapons_restricted_items, possess_drugs, possess_etc_tainted_property, possess_property_suspected_stolen, procuring_prostitution, produce_drugs, public_nuisance, public_soliciting, rape_and_attempted_rape, receiving_stolen_property, resist_incite_hinder_obstruct_police, sell_supply_drugs, serious_assault, serious_assault_other, shop_stealing, stalking, stealing_from_dwellings, stock_related_offences, trafficking_drugs, trespassing_and_vagrancy, unarmed_robbery, unlawful_entry_with_intent_dwelling, unlawful_entry_with_intent_other, unlawful_entry_with_intent_shop, unlawful_possess_concealable_firearm, unlawful_possess_firearm_other, unlawful_use_of_motor_vehicle, vehicles_steal_from_enter_with_intent, weapons_act_offences_other. 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.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely non-obvious operational facts: exact coverage bounds, data currency (2025-12-31), and a per-call price of 5¢, which matters for an agent deciding whether to spend a call. It does not mention pagination or result-size behavior.

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 blocks: what it returns, coverage bounds, and where to find full docs/price. Front-loaded with the substantive claim and no redundant restatement of the title or schema.

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?

No output schema exists, but the `fields` parameter enumerates the returnable columns and the description points to `/v1/datasets/recorded-crime-qld` for the field list and method, which covers most of the gap. Minor omissions remain around response shape/size and pagination for a 10-year multi-offence query.

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% — from/to formats, the lga_name format and the full field list are all documented in the schema itself. The description adds no parameter-level meaning beyond that, 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?

States a specific verb+resource+dimensions: 'Police-recorded offences in Queensland by council area, per year for 2016-2025, by offence type.' The geography (Queensland, council area) and time span implicitly separate it from the suburb-level and NSW/VIC siblings, but no alternative is named explicitly.

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 Coverage block (77 council areas, 2016-2025, current to 2025-12-31) tells the agent whether a query is answerable, which is useful implied guidance. However, there is no explicit when-to-use/when-not guidance, e.g. no pointer to the suburb-level or other-state equivalents for out-of-scope requests.

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