Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

LGA · Labour force status

lga_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": {
      "lga_name": "<lga_name>"
    },
    "name": "lga_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.
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.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely useful non-schema behavior: the 5¢ per-call price, the fixed 2021-08-10 snapshot, coverage counts (10,500 suburbs / 545 LGAs), and the exclusion of areas too small for reliable figures — the last being important for interpreting missing rows.

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?

Content description is front-loaded, followed by a compact Coverage block and a bolded price line, which is easy to scan. A little redundancy ('one snapshot at 10 August 2021. Current to 2021-08-10.') is the only waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and four parameters, the description covers cost, coverage and currency well, but says nothing about response shape, size or pagination, and does not warn that `lga_name` must match `/v1/lga/list` (that lives only in the schema). Adequate but leaving an agent to infer return behaviour.

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 carries the parameter burden and a 3 is the baseline. The description adds only indirect meaning — the single-snapshot note implies `from`/`to` have limited effect — and never mentions the time-range or field-subsetting parameters itself.

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 the specific subject matter precisely — full-time/part-time employment, unemployment, workforce exclusion, plus unemployment and participation rates — so an agent knows exactly what data comes back. The phrase 'for every suburb and council area' muddies it slightly given a separate suburbs sibling tool, but the LGA scope is unambiguous from the name and required 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?

No explicit when-to-use or when-not-to-use guidance, and no named alternative such as the suburbs equivalent. Usage is only implied by the coverage statement and the pointer to `/v1/datasets/labour-force` for full description and method, which does help an agent confirm fitness.

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