Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Suburb · Aboriginal and Torres Strait Islander residents

suburbs_area_stats_indigenous_status
Read-onlyIdempotent

How many residents are Aboriginal, Torres Strait Islander or both, and what share of the area that is, for every suburb and council area.

Coverage: About 11,000 suburbs and localities and 545 council areas across Australia, in all states and territories (areas with too few people or homes for reliable figures are left out); one snapshot at 10 August 2021. Current to 2021-08-10. Full description, field list and method: /v1/datasets/indigenous-status.

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

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: total_population, indigenous_count, indigenous_pct, aboriginal_count, aboriginal_pct, torres_strait_islander_count, torres_strait_islander_pct, both_aboriginal_and_torres_strait_islander_count, both_aboriginal_and_torres_strait_islander_pct, non_indigenous_count, non_indigenous_pct, indigenous_status_not_stated_count, indigenous_status_not_stated_pct. 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

A3.8/5.0
Behavior4/5

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

Annotations already establish a safe, idempotent, non-destructive read, so the description earns credit for what they cannot say: the universe size (~11,000 suburbs, 545 council areas), the exclusion of areas with too few people for reliable figures, the single 10 August 2021 snapshot, and a per-call price of 5¢. Pricing and coverage limits are exactly the operational context an agent needs before calling. Return format and percentage scale remain undisclosed.

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?

Three short blocks: the core question first, then coverage and currency, then the pointer and price. Almost nothing is wasted, though 'one snapshot at 10 August 2021' and 'Current to 2021-08-10' restate the same fact.

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 supplies the coverage universe, temporal currency, exclusion rules and cost, and it defers field-level detail to a documented endpoint while the fields parameter enumerates them. What is missing is how the suburb-vs-council-area scope interacts with the required suburb_name, and any indication of result shape.

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 all four parameters (suburb_name, from, to, fields) are fully documented with formats and an explicit field list, making the baseline 3 appropriate. The description adds no parameter-level meaning of its own, and notably does not reconcile the required suburb_name with its claim of covering council areas.

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 leads with a specific question-shaped verb+resource: counts of Aboriginal, Torres Strait Islander or both residents and their share, for suburbs and council areas. It is clearly distinguishable from the many other suburbs_area_stats_* siblings by topic. It stops short of naming the closest sibling (lga_area_stats_indigenous_status), and the claim of council-area coverage sits oddly against a suburb_name-only parameter.

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 agent can infer this is the tool for Indigenous-status demographics for a given area, and the coverage note explains that small areas are omitted, which is a useful eligibility caveat. There is no explicit when-to-use/when-not guidance and no pointer to the LGA-level or other-topic alternatives.

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