Skip to main content
Glama

Microburbs Australian Property Data

LGA · Income by birthplace

lga_area_stats_income_by_birthplace
Read-onlyIdempotent

How much each migrant community earns: weekly personal income bands by region of birth (nine world regions), in every suburb and council area.

Coverage: About 10,800 suburbs and localities and 545 council areas across Australia, in all states and territories (areas with too few residents 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/income-by-birthplace.

Price: 10¢ 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_income_by_birthplace"
  }
}

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_income_stated, all_under_500_pct, all_500_to_999_pct, all_1000_to_1999_pct, all_2000_plus_pct, oceania_income_stated, oceania_under_500_count, oceania_under_500_pct, oceania_500_to_999_count, oceania_500_to_999_pct, oceania_1000_to_1999_count, oceania_1000_to_1999_pct, oceania_2000_plus_count, oceania_2000_plus_pct, north_west_europe_income_stated, north_west_europe_under_500_count, north_west_europe_under_500_pct, north_west_europe_500_to_999_count, north_west_europe_500_to_999_pct, north_west_europe_1000_to_1999_count, north_west_europe_1000_to_1999_pct, north_west_europe_2000_plus_count, north_west_europe_2000_plus_pct, southern_eastern_europe_income_stated, southern_eastern_europe_under_500_count, southern_eastern_europe_under_500_pct, southern_eastern_europe_500_to_999_count, southern_eastern_europe_500_to_999_pct, southern_eastern_europe_1000_to_1999_count, southern_eastern_europe_1000_to_1999_pct, southern_eastern_europe_2000_plus_count, southern_eastern_europe_2000_plus_pct, middle_east_north_africa_income_stated, middle_east_north_africa_under_500_count, middle_east_north_africa_under_500_pct, middle_east_north_africa_500_to_999_count, middle_east_north_africa_500_to_999_pct, middle_east_north_africa_1000_to_1999_count, middle_east_north_africa_1000_to_1999_pct, middle_east_north_africa_2000_plus_count, middle_east_north_africa_2000_plus_pct, south_east_asia_income_stated, south_east_asia_under_500_count, south_east_asia_under_500_pct, south_east_asia_500_to_999_count, south_east_asia_500_to_999_pct, south_east_asia_1000_to_1999_count, south_east_asia_1000_to_1999_pct, south_east_asia_2000_plus_count, south_east_asia_2000_plus_pct, north_east_asia_income_stated, north_east_asia_under_500_count, north_east_asia_under_500_pct, north_east_asia_500_to_999_count, north_east_asia_500_to_999_pct, north_east_asia_1000_to_1999_count, north_east_asia_1000_to_1999_pct, north_east_asia_2000_plus_count, north_east_asia_2000_plus_pct, southern_central_asia_income_stated, southern_central_asia_under_500_count, southern_central_asia_under_500_pct, southern_central_asia_500_to_999_count, southern_central_asia_500_to_999_pct, southern_central_asia_1000_to_1999_count, southern_central_asia_1000_to_1999_pct, southern_central_asia_2000_plus_count, southern_central_asia_2000_plus_pct, americas_income_stated, americas_under_500_count, americas_under_500_pct, americas_500_to_999_count, americas_500_to_999_pct, americas_1000_to_1999_count, americas_1000_to_1999_pct, americas_2000_plus_count, americas_2000_plus_pct, sub_saharan_africa_income_stated, sub_saharan_africa_under_500_count, sub_saharan_africa_under_500_pct, sub_saharan_africa_500_to_999_count, sub_saharan_africa_500_to_999_pct, sub_saharan_africa_1000_to_1999_count, sub_saharan_africa_1000_to_1999_pct, sub_saharan_africa_2000_plus_count, sub_saharan_africa_2000_plus_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 this a read-only, idempotent, non-destructive, closed-world call. The description adds genuinely useful context beyond that: 10¢ per call pricing, ~10,800 suburb/545 LGA coverage, suppression of areas with too few residents, and a single 10 August 2021 snapshot. It does not cover result ordering, pagination, or default field behavior, so it sits at adequate rather than rich.

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?

Front-loads the core purpose in one sentence, then labels Coverage and Price in a compact structure. Minor waste in the duplicated recency statements ('one snapshot at 10 August 2021' and 'Current to 2021-08-10') and in the pointer to an external doc.

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?

For a read-only statistical query with no output schema, the description supplies the essentials: subject matter, geography, time coverage, suppression caveat, and cost. The main omission is disambiguating LGA-level results from the suburb-level sibling, which the 'every suburb and council area' phrasing actively blurs.

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 lga_name format, from/to formats, and the full field list are already documented. The description only re-frames the field list as 'nine world regions' with income bands, adding modest conceptual context rather than new parameter meaning.

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 concrete resource and measure: weekly personal income bands by region of birth (nine world regions) for Australian council areas. It is clear what data comes back, though the phrase 'in every suburb and council area' muddies the LGA-only scope implied by the tool name and title.

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?

No when-to-use or when-not-to-use guidance and no mention of the obvious alternative, suburbs_area_stats_income_by_birthplace, or neighbouring LGA datasets. Only coverage and price are given, leaving the agent to infer selection from the name alone.

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