Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

LGA · Unpaid work and care

lga_area_stats_unpaid_work_and_care
Read-onlyIdempotent

How many adults care, unpaid, for a person with a disability, illness or old age, look after children, and do housework (by hours a week), for every suburb and council area.

Coverage: About 10,500 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/unpaid-work-and-care.

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

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_aged_15_plus, unpaid_carers_count, unpaid_carers_pct, no_unpaid_assistance_count, no_unpaid_assistance_pct, unpaid_assistance_not_stated_count, unpaid_assistance_not_stated_pct, cared_for_children_count, cared_for_children_pct, cared_for_own_children_only_count, cared_for_own_children_only_pct, cared_for_other_children_only_count, cared_for_other_children_only_pct, cared_for_own_and_other_children_count, cared_for_own_and_other_children_pct, no_child_care_count, no_child_care_pct, child_care_not_stated_count, child_care_not_stated_pct, domestic_work_any_count, domestic_work_any_pct, domestic_work_under_5_hours_count, domestic_work_under_5_hours_pct, domestic_work_5_14_hours_count, domestic_work_5_14_hours_pct, domestic_work_15_29_hours_count, domestic_work_15_29_hours_pct, domestic_work_30_plus_hours_count, domestic_work_30_plus_hours_pct, no_domestic_work_count, no_domestic_work_pct, domestic_work_not_stated_count, domestic_work_not_stated_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

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behaviour, so the description only needs incremental context and it supplies real value: a fixed 10 August 2021 snapshot, exclusion of areas with too few people/homes, ~10,500 suburb and 545 LGA coverage, and a per-call price. It doesn't describe result shape or pagination, but with no output schema and strong annotations this is solid disclosure.

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-loaded with a plain-language question that defines the data, followed by a labelled Coverage block, currency date, doc pointer and price. Dense but each line is informative; only the 'suburb and council area' phrase is wasted ambiguity.

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 tool with full schema coverage and no output schema, the definition supplies the snapshot date, geographic scope, exclusion rules, cost and a documentation path. Missing only the return shape/units, which is a minor gap given the self-describing field names and the linked dataset endpoint.

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%, including `lga_name` format, `from`/`to` formats and an enumerated field list, so the schema carries the parameter burden. The description adds only indirect meaning ('by hours a week' framing the domestic_work_* fields and the single-snapshot note that effectively pins from/to), which is marginal beyond the schema.

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 a specific subject (unpaid care for a person with disability/illness/old age, child care, housework by hours per week) and the geographic unit (council areas). It is slightly muddied by saying 'for every suburb and council area' on a tool whose name and required `lga_name` param are LGA-only, which blurs the boundary with the suburbs sibling.

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?

It gives coverage constraints (single 2021 snapshot, small areas excluded, price per call) but no explicit when-to-use/when-not guidance and never names the suburbs equivalent for suburb-level queries despite that being the most likely selection error. The agent must infer routing from the tool name alone.

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