Microburbs Australian Property Data

LGA · Population projections (NSW)

lga_demographics_population_projections_nsw

Read-onlyIdempotent

Projected resident population of every New South Wales council area, 2021 to 2041, every year, with five age bands. Modelled estimates.

Coverage: NSW: 129 council areas; every year 2021-2041 (figures at 30 June). Current to 2041-06-30. Full description, field list and method: /v1/datasets/population-projections-nsw.

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

Input Schema

Name	Required	Description
`to`	No	Last period to include, same formats as `from`.
`from`	No	First period to include: 2020, 2020-Q3, 2020-07 or 2020-07-01.
`fields`	No	Comma-separated subset of: total_population, aged_0_14, aged_15_24, aged_25_44, aged_45_64, aged_65_plus. Omit for all.
`lga_name`	Yes	Council (LGA) name exactly as /v1/lga/list returns it, e.g. `Lake Macquarie`.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 13, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the description correctly spends its words elsewhere: it flags the data as modelled estimates (a real misuse risk), discloses per-call pricing of 5¢, states the 129-LGA coverage and the 2041-06-30 currency. It stops short of describing response shape or row limits for a 129-area × 21-year result set, which is the remaining behavioral gap.

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-loads scope in the first sentence, then a bolded caveat, then a compact coverage/currency block, then cost and a docs pointer. No sentence repeats the name or the schema, and the pricing line is short and unambiguous.

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, well-annotated, fully-schema-documented tool with no output schema, the description supplies the scope, granularity, caveat, cost and a docs pointer — enough to call it correctly. The one omission is any hint of the returned record structure or pagination behavior for what is potentially a large multi-year result.

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 `from`, `to`, `fields` and `lga_name` are already documented with formats and examples. The description adds only the framing that age bands exist and that `lga_name` must be the exact LGA name, both of which the schema already conveys. Baseline 3 applies.

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?

Names a specific resource (projected resident population), a precise geographic scope (every NSW council area), a temporal range (2021-2041, every year, 30 June), and a shape (five age bands, modelled estimates). An agent can tell this is the NSW projection series rather than a history or another state's series, but the description never names the sibling that serves those adjacent needs.

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 through the coverage statement and the pointer to `/v1/datasets/population-projections-nsw` for method. It never states when to prefer this over `lga_population` or the QLD/VIC projection siblings, nor any exclusion such as 'not for historical counts'.

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 tools Inspect

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

Need Help?