Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Suburb · Birthplace

suburbs_area_stats_birthplace
Read-onlyIdempotent

Where residents were born: counts and shares for the top 43 countries, plus Australia and other, in every suburb and council area.

Coverage: About 11,000 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/birthplace.

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_area_stats_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: total_population, australia_count, australia_pct, england_count, england_pct, india_count, india_pct, china_count, china_pct, new_zealand_count, new_zealand_pct, philippines_count, philippines_pct, vietnam_count, vietnam_pct, south_africa_count, south_africa_pct, malaysia_count, malaysia_pct, italy_count, italy_pct, sri_lanka_count, sri_lanka_pct, nepal_count, nepal_pct, scotland_count, scotland_pct, south_korea_count, south_korea_pct, united_states_count, united_states_pct, germany_count, germany_pct, hong_kong_count, hong_kong_pct, iraq_count, iraq_pct, greece_count, greece_pct, pakistan_count, pakistan_pct, lebanon_count, lebanon_pct, indonesia_count, indonesia_pct, thailand_count, thailand_pct, ireland_count, ireland_pct, iran_count, iran_pct, fiji_count, fiji_pct, netherlands_count, netherlands_pct, singapore_count, singapore_pct, afghanistan_count, afghanistan_pct, bangladesh_count, bangladesh_pct, canada_count, canada_pct, taiwan_count, taiwan_pct, brazil_count, brazil_pct, poland_count, poland_pct, japan_count, japan_pct, croatia_count, croatia_pct, egypt_count, egypt_pct, north_macedonia_count, north_macedonia_pct, zimbabwe_count, zimbabwe_pct, myanmar_count, myanmar_pct, cambodia_count, cambodia_pct, turkey_count, turkey_pct, france_count, france_pct, malta_count, malta_pct, not_stated_count, not_stated_pct, other_countries_count, other_countries_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, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful context beyond that: ~11,000 suburbs and 545 council areas, suppression of areas with too few residents, a single 2021-08-10 snapshot, and a per-call price — all things an agent could not infer from the annotations.

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, recency, doc pointer and price in a compact block. Minor redundancy between 'one snapshot at 10 August 2021' and 'Current to 2021-08-10', but nothing wasteful enough to obscure the call.

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?

Four parameters with full schema coverage, no output schema, and annotations covering the safety profile; the description supplies coverage, suppression, temporal scope and cost, which is most of what an agent needs. It does not describe the response shape or how counts and shares are paired, though the field list in the schema largely compensates.

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 the field list, period formats and suburb_name matching rule are already documented. The description's only parameter-relevant contribution is the cardinality of the country set and the note that data is a single snapshot, which implicitly limits what from/to can do; no extra syntax or semantics are supplied.

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 first sentence gives a specific resource (birthplace counts and shares for the top 43 countries plus Australia and other) and scope (every suburb and council area), which separates it from council-only siblings such as lga_area_stats_birthplace. It never names an alternative tool outright, so differentiation is inferred from the geography wording rather than stated.

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: query resident birthplace composition for a suburb or council area, with the exact dataset documented at /v1/datasets/birthplace. There is no explicit statement of when to prefer this over suburbs_ethnicity_birthplace or the lga_ variants, and no exclusions or prerequisites beyond the coverage note.

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