Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

LGA · Migration and population change

lga_area_stats_migration
Read-onlyIdempotent

Where people are moving: arrivals, departures and net moves from elsewhere in Australia and from overseas, plus births, deaths and population, for every council area per year since 2016-17.

Coverage: 543 council areas; years to 30 June 2017 through 2025 (nine years). Period is the first day of the financial year. Current to 2025-06-30. Full description, field list and method: /v1/datasets/migration.

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

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: net_internal_migration, internal_arrivals, internal_departures, net_overseas_migration, overseas_arrivals, overseas_departures, births, deaths, natural_increase, resident_population. 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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-obvious operational facts: a per-call price of 5¢, the temporal currency boundary of 2025-06-30, and that the period column is the first day of the financial year. It does not describe result shape or any row/size limits.

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?

Two short blocks: a front-loaded content sentence followed by a coverage block that carries the LGA count, year span, currency date and price. Nothing is repeated from the schema and no sentence is filler.

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, four-parameter data-retrieval tool with no output schema, the definition supplies the domain, spatial and temporal coverage, currency, cost and a documentation pointer. The remaining gap is return-format expectations (row shape, ordering, any row caps), which an agent would have to discover by calling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description adds the valid temporal window (years ending 30 June 2017 through 2025) that constrains `from`/`to`, and the period-alignment rule for those values. The narrative field mentions (arrivals, departures, net moves, births, deaths, population) also map onto the enumerated `fields` list.

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 the specific subject matter — arrivals, departures, net internal and overseas moves, births, deaths and resident population — for every council area per financial year, which distinguishes it from the many other lga_area_stats_* topic tools. It never explicitly names a sibling to defer to, so it stops short of full differentiation.

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 limits (543 LGAs, 2017 through 2025, current to 2025-06-30) and the 5¢ per-call price give useful context for deciding to call, and the pointer to `/v1/datasets/migration` offers deeper documentation. However, there is no explicit when-to-use/when-not guidance relative to neighbouring tools such as lga_population or the population-projection tools, leaving the choice to inference from the topic name.

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