Microburbs Australian Property Data

Terrain by mesh block (by suburb)

suburbs_mesh_blocks_terrain

Read-onlyIdempotent

Ground elevation and slope for every residential mesh block: median, lowest and highest ground level, typical and steepest slope, and the share of homes on flat or steep land.

Coverage: All states and territories; blocks with at least three addressed properties. Current to 2026-10-01. Full description, field list and method: /v1/datasets/terrain-block.

One call returns every mesh block in the suburb.

Price: 20¢ 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_mesh_blocks_terrain"
  }
}

Input Schema

Name	Required	Description	Default
`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.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 the safety profile is covered. The description adds real value beyond that: a hard cost of 20¢ per call, a data-currency date (2026-10-01), and an inclusion threshold that silently drops small blocks — behavior an agent must know before quoting results. It does not say what an empty or unmatched suburb response looks like.

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?

Metrics are front-loaded in the first sentence, followed by coverage, freshness, a doc pointer, cardinality and price — each sentence carries distinct information. Slightly list-like and the bolded price line is a formatting flourish, but nothing is wasted.

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, the description does the right thing by enumerating the returned measures, noting one-call-returns-all cardinality, the coverage threshold and the data vintage. Still missing are the response shape/units (metres? degrees?), how non-residential or mixed blocks are treated, and error behavior for an unknown suburb name.

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?

Only one parameter exists and schema coverage is 100%, with the schema itself specifying the exact format ('as /v1/suburbs/list returns it', with the 'St Kilda (Vic.)' disambiguation example). The description adds nothing about the parameter, so the baseline of 3 applies.

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 resource (residential mesh blocks), the geographic scope (by suburb), and enumerates the actual metrics returned: median/lowest/highest ground level, typical and steepest slope, share of flat or steep land. That is far more specific than a restatement of the title, though it never names a sibling (e.g. properties_environment_terrain or suburbs_mesh_blocks_environment) to draw the boundary.

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 context is implied rather than stated: 'One call returns every mesh block in the suburb' and the coverage rule 'blocks with at least three addressed properties' tell an agent when the data is applicable and that no pagination is needed. There is no explicit when-to-use/when-not-to-use guidance or named alternative tool for property-level or state-level terrain queries.

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?