Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Suburb · Contaminated and regulated sites

suburbs_environment_contaminated_land
Read-onlyIdempotent

How many mapped contaminated or regulated sites sit inside a suburb, how many are within 1 km of its centre, and how far the nearest one is, for NSW, Victoria, Queensland, South Australia and Western Australia.

Coverage: NSW, Vic, Qld, SA and WA suburbs only (14,124 suburbs); no rows for Tas, ACT, NT or other territories. Current to 2026-10-01. Full description, field list and method: /v1/datasets/contaminated-land.

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

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: sites_mapped, sites_within_1km_of_centre, sites_per_km2, nearest_site_m. 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

A4/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 the safety profile is covered. The description adds value beyond that with the geographic coverage limit (14,124 suburbs, five states only), the data currency date (2026-10-01), and a per-call price of 5¢ — a cost signal an agent should factor in before calling repeatedly. It does not describe result ordering or empty-result 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?

Front-loaded with what is returned, then coverage limits, currency, documentation pointer, and price — each sentence carries distinct information an agent needs. Bolded price and the docs path are scannable without padding.

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 does the necessary work of enumerating the returned metrics and flagging the state coverage gap, and it routes to /v1/datasets/contaminated-land for field definitions and method. It stops short of clarifying units for the nearest-site distance or what counts as a 'regulated' site, leaving those to the external doc.

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 every parameter (suburb_name, from, to, fields) is already documented with formats and examples in the schema. The description names the same metrics that `fields` accepts but adds no syntax, defaults, or matching rules beyond what the schema supplies, so the baseline of 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?

The opening sentence names the exact measures returned: count of mapped contaminated/regulated sites in a suburb, count within 1 km of the centre, and distance to the nearest site. The resource (contaminated/regulated sites) is specific enough to separate it from the other suburbs_environment_* datasets such as aircraft noise, climate normals or heat and extremes, without needing to name them.

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 by the coverage note: it warns there are no rows for Tas, ACT, NT or other territories, which effectively tells an agent when the tool will return nothing. There is no explicit statement of when to prefer this over a sibling dataset, no prerequisites, and no guidance on how to obtain a valid suburb name beyond the schema's pointer to /v1/suburbs/list.

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