Microburbs Australian Property Data

Transport by mesh block — stops, stations, commuting (by suburb)

suburbs_mesh_blocks_transport

Read-onlyIdempotent

How do you get around from here? For every mesh block in the suburb: distance to the nearest bus stop, train station and tram stop, bus stops within 320 m, and how many workers commute by public transport.

One entry per mesh block in the suburb under mesh_blocks, each with its mb_code, population and dwellings. Values only — the matching polygons come from /shapes/mesh-blocks.

Every field carries provenance — measured (at this block), measured_wider_area (measured for the SA1 or postcode and repeated on every block in it), estimate (our model) or not_recorded (not labelled yet) — plus how, one sentence on how the number was arrived at (empty when not_recorded).

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

Input Schema

Name	Required	Description	Default
`suburb_name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A3.5/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 the safety profile is covered. The description goes further by disclosing the return shape (one entry per mesh block under `mesh_blocks`, with mb_code, population, dwellings), the provenance taxonomy (measured / measured_wider_area / estimate / not_recorded) and the `how` field, which materially affect how an agent should interpret numbers.

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 a framing question, then field inventory, then the output-structure and provenance note. Every sentence carries information; the rhetorical opener is the only mild padding.

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?

With no output schema, the description does the necessary work of explaining the response container, per-block fields, and provenance semantics. The remaining gap is input-side: nothing tells the agent how the suburb_name must be formed.

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

Parameters2/5

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

Schema coverage is 0% for the single parameter, so the description must carry the load, but it never explains what suburb_name should contain or how it is matched (exact name, canonical name from suburbs_list, case sensitivity). 'In the suburb' only loosely implies it.

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 resource (transport access metrics per mesh block) and enumerates the measures: distance to nearest bus stop, train station and tram stop, bus stops within 320 m, and public-transport commuting counts. It is clearly a retrieval tool for a suburb's mesh blocks, distinguishable from geometry siblings by the explicit note that polygons come from /shapes/mesh-blocks. It doesn't explicitly differentiate from properties_transport_nearby or suburbs_shapes_mesh_blocks, keeping it from a 5.

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 rather than stated: the tool is for answering 'how do you get around from here' at mesh-block granularity, and one routing hint is given (get polygons from /shapes/mesh-blocks). There is no explicit when-to-use vs. when-not or a named alternative for point-level transport data.

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?