Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Suburb · Occupation

suburbs_area_stats_occupation
Read-onlyIdempotent

What working residents do: managers, professionals, trades, community and personal service, clerical, sales, machinery operators and labourers, as counts and shares of employed residents for every suburb and council area.

Coverage: About 8,800 suburbs and localities and 540 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/occupation.

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

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_employed, managers_count, managers_pct, professionals_count, professionals_pct, technicians_and_trades_count, technicians_and_trades_pct, community_and_personal_service_count, community_and_personal_service_pct, clerical_and_administrative_count, clerical_and_administrative_pct, sales_count, sales_pct, machinery_operators_and_drivers_count, machinery_operators_and_drivers_pct, labourers_count, labourers_pct, occupation_not_stated_count, occupation_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.9/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, so the safety profile is covered. The description adds real behavioural context the annotations do not: dataset extent (~8,800 suburbs, 540 council areas, all states), a single snapshot at 10 August 2021, exclusion of areas too small for reliable figures, and a per-call price of 5¢ — the latter two materially affect whether an agent should call it.

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 purpose sentence, followed by coverage, a documentation pointer, and price — each sentence carries information an agent needs. Slightly dense with the occupation enumeration, but nothing is redundant.

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 data-retrieval tool with no output schema, the description conveys what is returned (counts and shares per occupation category) and points to a field list at /v1/datasets/occupation. Remaining gaps are minor: response shape/pagination and the 5¢ pricing mechanics (per call regardless of size) are not spelled out.

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 suburb_name format, the fields list, and the from/to date formats; baseline 3 applies. The description adds only the snapshot date, which implicitly signals that from/to are of limited use here, but it does not explain that interaction explicitly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names the exact content (occupation counts and shares of employed residents) plus the exact geography (every suburb and council area), and enumerates the occupation categories so an agent can tell this apart from the labour-force, education, or travel-to-work siblings without opening any schema.

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 subject matter and the coverage note, but there is no explicit when-to-use/when-not guidance and no sibling alternative named (e.g. lga_area_stats_occupation or suburbs_area_stats_labour_force). The coverage sentence does usefully warn that small areas are excluded, which implicitly tells the agent when this tool will return nothing.

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