Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Suburb · Labour force status

suburbs_area_stats_labour_force
Read-onlyIdempotent

Who works full-time or part-time, who is unemployed and looking, and who is outside the workforce, with the unemployment and participation rates, 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/labour-force.

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

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, employed_count, employed_pct, employed_full_time_count, employed_full_time_pct, employed_part_time_count, employed_part_time_pct, employed_away_from_work_count, employed_away_from_work_pct, unemployed_count, unemployed_pct, labour_force_count, labour_force_pct, not_in_labour_force_count, not_in_labour_force_pct, unemployment_rate. 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 declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: a 5¢ per-call price, the exact data vintage (10 Aug 2021), and the exclusion rule that areas with too few people/homes are omitted — all of which affect whether an agent should call it and how to interpret sparse results. It does not describe response shape or pagination, but no output schema exists so that is a modest gap.

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 the substantive content, then coverage, then price — a sensible order with no filler sentences. Minor redundancy between 'one snapshot at 10 August 2021' and 'Current to 2021-08-10', which say the same thing twice.

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 4-parameter read-only data lookup with no output schema, the definition supplies what an agent needs: what the measures are, the geographic scope and its exclusions, the vintage, the cost, and a doc link. The one incompleteness is that it never reconciles the from/to period parameters with the stated single-snapshot coverage, which could mislead an agent into expecting a time series.

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 the schema already documents every parameter including the field list and date formats. The description adds only an indirect aid — the /v1/datasets/labour-force link for the full field list — and does not clarify why from/to exist given the single 2021 snapshot. 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 names the specific measures returned (full-time/part-time employment, unemployment, participation) and the geography (suburbs and council areas), plus a pointer to the authoritative dataset doc. It does not, however, distinguish itself from the sibling lga_area_stats_labour_force, which covers the same measures for council areas only — the description's claim of covering both suburbs and 545 council areas blurs that boundary.

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 statement and the dataset link, and the snapshot date effectively tells the agent the data is one point in time. But there is no explicit statement of when to pick this tool over the lga sibling, and no guidance on how the from/to period filters interact with a single 2021 snapshot.

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