Microburbs Australian Property Data

Business by mesh block — shops, cafes and services nearby (by suburb)

suburbs_mesh_blocks_business

Read-onlyIdempotent

What's nearby? For every mesh block in the suburb: distance to the nearest supermarket, cafe, restaurant, bakery, pharmacy, GP and pub, and how many cafes, restaurants and supermarkets are within 320 m.

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

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?

Beyond the existing read-only and idempotent annotations, the description discloses important behavioral context: one entry per mesh block, values only, polygons obtained from a separate shape tool, and provenance labels explaining whether a value is measured locally, inherited from a wider area, estimated, or not recorded. This is substantial transparency, though it does not address error behavior or rate limits.

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?

The description is front-loaded with the core question and then organizes output details and provenance cleanly. It is reasonably concise, though the provenance explanation is dense and could be separated more clearly for scanning.

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?

Because there is no output schema, the description appropriately explains the returned structure, mesh block fields, and provenance semantics. It is nearly complete for calling the tool, but it leaves the required suburb_name input format under-specified, which is a meaningful gap for a single-parameter tool.

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 description coverage is 0%, and the single suburb_name parameter is not defined in the description beyond the general phrase 'in the suburb.' The description does not explain accepted suburb name format, matching rules, or whether state or postcode is required, so it does not compensate for the missing schema documentation.

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 clearly states the resource and scope: business amenity proximity and counts for every mesh block in a suburb, including the specific amenity types and 320 m radius. It is distinguishable from most siblings, though it does not explicitly differentiate itself from related tools such as suburbs_demographics_business or suburbs_lifestyle_pois.

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 'What's nearby?' framing and the suburb-level mesh block scope, so an agent can infer this is for block-level business amenity proximity. However, the description gives no explicit when-to-use guidance, no exclusions, and no alternatives for suburb-wide business counts or POI searches.

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?