Microburbs Australian Property Data

Suburb · Public transport access and service

suburbs_transport_public_transport

Read-onlyIdempotent

Stops by mode, weekday service frequency, routes, and how many addresses are within a short walk of a stop or station, for suburbs in Victoria, South East Queensland, Perth, Adelaide, Tasmania and Darwin.

Coverage: Victoria (trains, trams, buses, coaches), South East Queensland, the Perth region and the towns its bus network serves, Adelaide and its regional services, Tasmania, and Darwin. Not covered: New South Wales, the ACT, the rest of Queensland and the Northern Territory outside Darwin. A suburb is included when it is in a covered state and within 25 km of a stop; inside that area a suburb with no service shows real zeros. Current to 2026-11-06. Full description, field list and method: /v1/datasets/public-transport.

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

Input Schema

Name	Required	Description
`to`	No	Last period to include, same formats as `from`.
`from`	No	First period to include: 2020, 2020-Q3, 2020-07 or 2020-07-01.
`fields`	No	Comma-separated subset of: stops_total, stops_bus, stops_train, stops_tram, stops_ferry, weekday_trips_total, weekday_trips_bus, weekday_trips_train, weekday_trips_tram, weekday_trips_ferry, peak_trips_per_hour_busiest_stop, routes_total, routes_bus, routes_train, routes_tram, routes_ferry, share_addr_400m_stop_pct, share_addr_800m_station_pct, median_addr_distance_to_stop_m, nearest_train_station_m. Omit for all.
`suburb_name`	Yes	Suburb name exactly as /v1/suburbs/list returns it, e.g. `Bondi` or `St Kilda (Vic.)`.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 13, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare this a read-only, idempotent, non-destructive query, so the description is not responsible for the safety profile. It nonetheless adds real behavioural context the schema lacks: a 5¢ per-call price, a data currency date of 2026-11-06, the crucial zero-versus-absent distinction ('a suburb with no service shows real zeros'), and a pointer to the full method document.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The measure list is front-loaded, which is good, but the covered-state list is effectively repeated three times (intro sentence, Coverage paragraph, and again via the 25 km rule), and the pricing line is set off in bold at the end rather than surfaced earlier. The content is all relevant, but the repetition costs it.

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 dataset query with a fully documented four-parameter schema and no output schema, the description supplies everything an agent needs before calling: what is measured, where it applies, when it does not, what a zero means, how fresh the data is, what it costs, and where the method and field list live.

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 suburb_name, from, to and fields are already fully documented in the schema, including the exact-match requirement and the field-name enumeration. The description only restates the field families in prose ('stops by mode, weekday service frequency, routes'), adding no syntax or usage detail beyond the structured fields, which matches the baseline of 3.

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 opening sentence names the concrete measures (stops by mode, weekday service frequency, routes, addresses within a short walk) and the geography, so the resource is unambiguous. It does not name or distinguish itself from nearby siblings such as suburbs_mesh_blocks_public_transport_access or suburbs_transport_ev_chargers, leaving that differentiation to the agent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The Coverage paragraph effectively states when this tool is applicable and when it is not: NSW, ACT, non-SEQ Queensland and non-Darwin NT are excluded, and a suburb only qualifies if it is within 25 km of a stop. That is strong eligibility guidance, though it never routes the agent to a specific alternative tool for the uncovered areas.

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 tools Inspect

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

Need Help?