Skip to main content
Glama

Microburbs Australian Property Data

Suburb · Crime by time of day (Queensland)

suburbs_crime_offences_by_time_qld
Read-onlyIdempotent

When police-recorded offences happen in Queensland suburbs: counts and shares by 3-hour band and by day of week, over the last 12 months.

Coverage: Queensland: 2,584 suburbs with offences; 12 months to 2026-11-04. Current to 2026-11-04. Full description, field list and method: /v1/datasets/crime-time-of-day-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": {
      "suburb_name": "<suburb_name>"
    },
    "name": "suburbs_crime_offences_by_time_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: all_band_00_03_count, all_band_00_03_share, all_band_03_06_count, all_band_03_06_share, all_band_06_09_count, all_band_06_09_share, all_band_09_12_count, all_band_09_12_share, all_band_12_15_count, all_band_12_15_share, all_band_15_18_count, all_band_15_18_share, all_band_18_21_count, all_band_18_21_share, all_band_21_24_count, all_band_21_24_share, all_dow_monday_count, all_dow_monday_share, all_dow_tuesday_count, all_dow_tuesday_share, all_dow_wednesday_count, all_dow_wednesday_share, all_dow_thursday_count, all_dow_thursday_share, all_dow_friday_count, all_dow_friday_share, all_dow_saturday_count, all_dow_saturday_share, all_dow_sunday_count, all_dow_sunday_share, assault_band_00_03_count, assault_band_00_03_share, assault_band_03_06_count, assault_band_03_06_share, assault_band_06_09_count, assault_band_06_09_share, assault_band_09_12_count, assault_band_09_12_share, assault_band_12_15_count, assault_band_12_15_share, assault_band_15_18_count, assault_band_15_18_share, assault_band_18_21_count, assault_band_18_21_share, assault_band_21_24_count, assault_band_21_24_share, assault_dow_monday_count, assault_dow_tuesday_count, assault_dow_wednesday_count, assault_dow_thursday_count, assault_dow_friday_count, assault_dow_saturday_count, assault_dow_sunday_count, unlawful_entry_band_00_03_count, unlawful_entry_band_00_03_share, unlawful_entry_band_03_06_count, unlawful_entry_band_03_06_share, unlawful_entry_band_06_09_count, unlawful_entry_band_06_09_share, unlawful_entry_band_09_12_count, unlawful_entry_band_09_12_share, unlawful_entry_band_12_15_count, unlawful_entry_band_12_15_share, unlawful_entry_band_15_18_count, unlawful_entry_band_15_18_share, unlawful_entry_band_18_21_count, unlawful_entry_band_18_21_share, unlawful_entry_band_21_24_count, unlawful_entry_band_21_24_share, unlawful_entry_dow_monday_count, unlawful_entry_dow_tuesday_count, unlawful_entry_dow_wednesday_count, unlawful_entry_dow_thursday_count, unlawful_entry_dow_friday_count, unlawful_entry_dow_saturday_count, unlawful_entry_dow_sunday_count, vehicle_use_band_00_03_count, vehicle_use_band_00_03_share, vehicle_use_band_03_06_count, vehicle_use_band_03_06_share, vehicle_use_band_06_09_count, vehicle_use_band_06_09_share, vehicle_use_band_09_12_count, vehicle_use_band_09_12_share, vehicle_use_band_12_15_count, vehicle_use_band_12_15_share, vehicle_use_band_15_18_count, vehicle_use_band_15_18_share, vehicle_use_band_18_21_count, vehicle_use_band_18_21_share, vehicle_use_band_21_24_count, vehicle_use_band_21_24_share, vehicle_use_dow_monday_count, vehicle_use_dow_tuesday_count, vehicle_use_dow_wednesday_count, vehicle_use_dow_thursday_count, vehicle_use_dow_friday_count, vehicle_use_dow_saturday_count, vehicle_use_dow_sunday_count. 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.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world. The description adds genuinely new behavioral facts: the price (5¢ per call), the data coverage (2,584 suburbs, 12 months to 2026-11-04) and recency. It does not discuss result size, truncation, or what happens when a suburb has no offences, which keeps it below 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?

The opening sentence carries the payload and the coverage/price lines are clearly separated. Minor redundancy: the 12-month window to 2026-11-04 is stated twice ('over the last 12 months', '12 months to 2026-11-04', 'Current to 2026-11-04').

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?

With no output schema and four fully documented parameters, the description supplies the missing shape of the response (counts and shares by band and day of week) and the data vintage. It leaves unspecified whether suburb_name failures error or return empty, and what the default time window is when from/to are omitted.

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 documented, and the enum-free fields list is spelled out in-schema. The description's contribution is limited to confirming that outputs are counts and shares per band and day-of-week, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and measure — police-recorded offences by 3-hour band and day of week in Queensland suburbs — plus the temporal window (last 12 months). This distinguishes it from the plain offence-count siblings (e.g. suburbs_crime_recorded_offences_qld_suburbs) by what is actually returned, not just by name.

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 by the scoping ('in Queensland suburbs', 'by 3-hour band and by day of week'), which tells an agent what question this answers, but there is no explicit when-to-use vs when-not, and no named alternative for total-offence counts. The pointer to '/v1/datasets/crime-time-of-day-qld' is documentation routing rather than selection guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources