Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Suburb · Banking, post and emergency services

suburbs_amenities_services
Read-onlyIdempotent

Bank branches, ATMs, post offices, police stations and fire stations: counts in the suburb, rates per 1,000 residents and distance from the suburb centre to the nearest of each.

Coverage: All Australian suburbs and localities. Current to 2026-10-01. Full description, field list and method: /v1/datasets/services.

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

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: count_banks, per_1000_banks, nearest_km_banks, count_atms, per_1000_atms, nearest_km_atms, count_post_offices, per_1000_post_offices, nearest_km_post_offices, count_police_stations, per_1000_police_stations, nearest_km_police_stations, count_fire_stations, per_1000_fire_stations, nearest_km_fire_stations, count_total, per_1000_total, per_km2_total. Omit for all.
suburb_nameYesSuburb name exactly as /v1/suburbs/list returns it, e.g. `Bondi` or `St Kilda (Vic.)`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the bar is lower. The description adds genuinely useful context beyond that: national coverage, a currency date (2026-10-01), and an explicit per-call price of 5¢, which affects whether an agent should batch or avoid redundant calls.

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

Conciseness5/5

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

Leads with what the tool returns, then coverage and currency, then the price caveat and doc pointer. Every line is load-bearing and there is no filler.

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 carry the burden of explaining returns and does so (counts, rates, distances). Coverage and currency are stated. The only minor gap is that it does not say how the results are shaped (per-suburb single row vs. time series implied by from/to).

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 coverage is 100%, so suburb_name, from/to and fields are fully documented in the schema itself. The description's mention of counts, per-1,000 rates and nearest-km distances loosely maps to the field list but adds no format or usage detail beyond it; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names the exact resource categories (bank branches, ATMs, post offices, police and fire stations) and the exact measures returned (counts, rates per 1,000 residents, distance from suburb centre). This is enough to tell it apart from the adjacent amenities siblings such as health services or parks and recreation.

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 only implied by the enumerated categories; there is no explicit statement of when to pick this over a sibling amenities tool, nor any when-not condition. An agent must infer the boundary from the category list alone.

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