Microburbs Australian Property Data

LGA · Need for assistance

lga_area_stats_need_for_assistance

Read-onlyIdempotent

How many residents need help with everyday activities because of disability, long-term illness or old age, overall and among residents aged 65 and over, for 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 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/need-for-assistance.

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

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, need_assistance_count, need_assistance_pct, no_need_assistance_count, no_need_assistance_pct, need_assistance_not_stated_count, need_assistance_not_stated_pct, total_aged_65_plus, aged_65_plus_need_assistance_count, aged_65_plus_need_assistance_pct. 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.7/5.0

Behavior4/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 the safety profile is covered. The description adds genuinely useful behavior beyond that: a per-call price of 5¢, a fixed 10 August 2021 snapshot, and the caveat that areas with too few people or homes are excluded from results.

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 metric and the breakdown dimensions in the first sentence, then coverage, snapshot and price in compact form; nothing is padded. The phrase 'for every suburb and council area' is the one piece of wording that costs clarity rather than adding it.

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, single-snapshot statistics tool with a fully documented schema and annotations, the description covers what the numbers mean, the geography, the temporal snapshot and the cost. The main omission relative to tool complexity is the suburb-vs-LGA scope boundary, which matters because a similarly named sibling exists.

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%, with formats for `from`/`to`, the full field enumeration, and an example of `lga_name` already documented inline. The description adds no parameter-level detail beyond a dataset link, so the 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?

States a specific metric (residents needing help with everyday activities due to disability, long-term illness or old age), broken out overall and for 65+, and identifies the geography as council areas. Slight ambiguity: it claims coverage 'for every suburb and council area', which blurs the boundary with the sibling suburbs_area_stats_need_for_assistance even though this tool requires lga_name.

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 by the coverage note and the pointer to `/v1/datasets/need-for-assistance`, so an agent can infer this is the LGA-level view of the need-for-assistance dataset. It never explicitly says when to pick this over the suburb-level sibling, nor does it state the prerequisite that lga_name must come from `/v1/lga/list` in the description itself.

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?