Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

LGA · Method of travel to work

lga_area_stats_travel_to_work
Read-onlyIdempotent

How working residents got to work: car as driver or passenger, train, bus, tram, ferry, bike, walking, working from home, and the share using public transport, 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/travel-to-work.

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

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, public_transport_count, public_transport_pct, car_as_driver_count, car_as_driver_pct, car_as_passenger_count, car_as_passenger_pct, train_count, train_pct, bus_count, bus_pct, ferry_count, ferry_pct, tram_or_light_rail_count, tram_or_light_rail_pct, taxi_or_ride_share_count, taxi_or_ride_share_pct, truck_count, truck_pct, motorbike_or_scooter_count, motorbike_or_scooter_pct, bicycle_count, bicycle_pct, walked_only_count, walked_only_pct, other_single_method_count, other_single_method_pct, two_methods_count, two_methods_pct, two_methods_with_train_count, two_methods_with_train_pct, two_methods_with_bus_count, two_methods_with_bus_pct, three_methods_count, three_methods_pct, worked_at_home_count, worked_at_home_pct, did_not_go_to_work_count, did_not_go_to_work_pct, method_not_stated_count, method_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.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely non-structured behavior: a 5¢ per-call cost, a hard coverage cap (~8,800 suburbs, ~540 LGAs, small areas omitted), and a single fixed snapshot at 10 August 2021. It does not describe response shape or pagination, but that is a minor gap given the safety profile is already declared.

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 substance (what the data measures), followed by coverage, currency and cost in short blocks. Every sentence carries usable information, though the opening sentence is a dense enumeration that could be tightened.

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

Completeness5/5

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

For a read-only statistics tool with no output schema, the definition supplies what an agent needs: what is measured, geographic coverage and its exclusions, the snapshot date, per-call price, and a documentation pointer (/v1/datasets/travel-to-work) for field lists and method. The full field enumeration lives in the schema, so nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema lacks: the data is a single snapshot current to 2021-08-10, which tells the agent that from/to period filtering has essentially no effect. It also names the measurable modes that the fields parameter exposes, orienting the agent before it reads the long enum list.

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 a concrete verb+resource: how working residents travelled to work, enumerating modes (car as driver/passenger, train, bus, tram, ferry, bike, walking, WFH, public transport share). It is clear what data is returned, but it does not explicitly differentiate itself from the sibling suburbs_area_stats_travel_to_work — in fact 'for every suburb and council area' blurs that boundary, even though the lga_name parameter and title imply LGA-level only.

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 (suburbs and council areas, areas with too few people excluded) and the snapshot date, but there is no explicit when-to-use/when-not guidance and no named alternative such as the suburbs variant. The price note gives a reason to economize calls but not a routing rule.

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