Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Suburb · Aircraft noise zones

suburbs_environment_aircraft_noise
Read-onlyIdempotent

How much of a suburb or city block sits inside the published aircraft-noise zones around Australian airports: share of addresses in each noise band, the loudest band, and whether the airport has a night curfew.

Coverage: About 250 suburbs and 4,700 blocks have at least one address inside a published zone (NSW, VIC, QLD, SA, WA, NT); about 1,700 more suburbs and 110,000 blocks within 20 km of such an airport are listed at 0%. Everywhere else, and Brisbane, Hobart and Canberra, is not listed. Current to 2026-10-19. Full description, field list and method: /v1/datasets/aircraft-noise.

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

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: addresses_total, addresses_in_zone, in_zone_share_pct, band_15_20_pct, band_20_25_pct, band_25_30_pct, band_30_plus_pct, highest_anef_band, curfew_airport_share_pct, approx_zone_share_pct. 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.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent and non-destructive, so the description does not need to restate safety. It instead adds genuinely new behavioral facts: the coverage footprint and its exceptions, the currency date (2026-10-19), and a per-call price of 5¢, which matters for an agent budgeting calls.

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 first sentence front-loads the output content, then coverage, freshness and price each get their own short block with bolded callouts. It is dense but every sentence carries information; the coverage sentence is the longest and could be trimmed slightly.

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, the description compensates by naming the returned quantities (band shares, highest band, curfew share) and pointing to the field list and method at a linked endpoint. Given 100% schema coverage of the four inputs, the only residual gap is that no sibling routing guidance is given.

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%, with every parameter including the field list documented in the schema itself. The description adds no parameter-level meaning beyond the schema, so the baseline of 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?

The description names a specific measure (share of addresses per aircraft-noise band, loudest band, curfew flag) for a specific resource (suburb), which is concrete. It is slightly muddied by the phrase 'suburb or city block', which blurs the boundary with the mesh-block sibling, but the core purpose is unmistakable.

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?

Coverage and exclusion rules (NSW/VIC/QLD/SA/WA/NT listed; Brisbane, Hobart and Canberra not listed; 20 km buffer shown at 0%) do tell an agent when the tool will return data. However, there is no explicit statement of when to use this suburb-level tool rather than suburbs_mesh_blocks_aircraft_noise or suburbs_shapes_noise_heatmap, leaving the main routing decision to inference.

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