Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Suburb · Unpaid work and care

suburbs_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": {
      "suburb_name": "<suburb_name>"
    },
    "name": "suburbs_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.
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 cover the safety profile (readOnly, idempotent, non-destructive), so the description adds genuinely new behavioral facts: the dataset covers ~10,500 suburbs and 545 councils with small areas omitted, a single snapshot at 10 August 2021, and a per-call price of 5¢. Cost and data-freshness disclosure are exactly the kind of context an agent needs before invoking, though nothing is said about pagination, row limits, or response shape.

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?

The opening sentence front-loads the subject matter and the remaining paragraphs are short and scannable (coverage, freshness, docs link, price). The long parenthetical enumeration of care types is reasonably economical given it defines the measure, and nothing is redundant with the title.

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?

With no output schema, the description carries return-shape burden and partially meets it by pointing to `/v1/datasets/unpaid-work-and-care` for the field list and method. Combined with annotations and a fully documented input schema, an agent has enough to call correctly; the only real gap is silence on result volume/pagination for a per-suburb query.

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 coverage is 100%, so `suburb_name`, `from`, `to`, and `fields` are already fully documented in the schema, including the accepted date formats and the complete field list. The description adds no parameter-level meaning beyond that — notably it never clarifies that `from`/`to` are largely moot for a single-snapshot 2021 dataset, which would have been useful. 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?

The description states concretely what is measured — unpaid care for a person with a disability/illness/old age, child care, and housework by hours per week — and the geographic scope (every suburb and council area). It clearly distinguishes itself from the LGA-oriented siblings by naming the suburb/council-area breakdown, though the title 'Suburb' versus the body's 'suburb and council area' leaves a small ambiguity about whether the LGA sibling is required for council-only queries.

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 rather than stated: an agent can infer this is the tool for unpaid-work-and-care figures at suburb level, and the coverage note warns that small areas are excluded. There is no explicit when-to-use versus the sibling `lga_area_stats_unpaid_work_and_care`, and no guidance that `suburb_name` must first be resolved via `/v1/suburbs/list` (that hint appears only in the schema).

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