Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

LGA · Year of arrival

lga_area_stats_year_of_arrival
Read-onlyIdempotent

When overseas-born residents arrived in Australia: from before 1951 to 2021, with a recent-arrivals total, for every suburb and council area.

Coverage: About 5,200 suburbs and localities and 505 council areas across Australia, in all states and territories (areas with too few people or homes for reliable figures are left out); one snapshot at 10 August 2021. Current to 2021-08-10. Full description, field list and method: /v1/datasets/year-of-arrival.

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

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_born_overseas, arrived_2016_to_2021_count, arrived_2016_to_2021_pct, arrived_before_1951_count, arrived_before_1951_pct, arrived_1951_1960_count, arrived_1951_1960_pct, arrived_1961_1970_count, arrived_1961_1970_pct, arrived_1971_1980_count, arrived_1971_1980_pct, arrived_1981_1990_count, arrived_1981_1990_pct, arrived_1991_2000_count, arrived_1991_2000_pct, arrived_2001_2010_count, arrived_2001_2010_pct, arrived_2011_2015_count, arrived_2011_2015_pct, arrived_2016_count, arrived_2016_pct, arrived_2017_count, arrived_2017_pct, arrived_2018_count, arrived_2018_pct, arrived_2019_count, arrived_2019_pct, arrived_2020_count, arrived_2020_pct, arrived_2021_count, arrived_2021_pct, arrived_not_stated_count, arrived_not_stated_pct. 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

B3.2/5.0
Behavior3/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 usefully adds facts the annotations cannot express: snapshot date (10 August 2021), exclusion of areas with too few people, exact coverage counts, and a per-call price, though it omits return format and pagination behavior.

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?

Purpose is front-loaded, followed by coverage, then price, so the agent hits the important information first. Minor waste in restating the snapshot date twice ('10 August 2021' and 'Current to 2021-08-10').

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the agent must learn elsewhere how rows are returned and at what granularity, and the suburb-versus-LGA distinction is not resolved. Coverage, currency and cost are nevertheless well covered for a read-only statistics endpoint.

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%, and the field list, date formats and lga_name format are all documented in the schema itself. The description only adds the idea of a 'recent-arrivals total', which is marginal beyond what the schema already provides.

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 states a specific resource (year-of-arrival data for overseas-born residents) with concrete scope: bands from before 1951 to 2021, a recent-arrivals total, and per-LGA coverage. It is weakened by saying 'for every suburb and council area', which blurs the distinction from the sibling suburbs_area_stats_year_of_arrival tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains what the data is and points to /v1/datasets/year-of-arrival for method details, but gives no guidance on when to choose this LGA variant over the suburb variant or other lga_area_stats topics. The agent must infer selection from the tool name alone.

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