Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

LGA · Aboriginal and Torres Strait Islander residents

lga_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": {
      "lga_name": "<lga_name>"
    },
    "name": "lga_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.
lga_nameYesCouncil (LGA) name exactly as /v1/lga/list returns it, e.g. `Lake Macquarie`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/closed-world, and the description adds real value on top: ~11,000 suburbs and 545 council areas, exclusion of areas with too-few people, a fixed 10 August 2021 snapshot, and a per-call price. It does not mention result-size limits or pagination, so it stops short of a 5.

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?

Lead sentence answers the core question first, then coverage, then currency, then doc link, then price — a sensible front-loaded order with little waste. The parenthetical about excluded small areas is dense but earns its place by setting expectations about missing rows.

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?

For a single-required-parameter read tool with full schema coverage and annotations covering safety, the description supplies the missing operational context: geographic scope, temporal currency, exclusions, and cost. Remaining gaps (return shape beyond counts/shares, row limits) are minor since no output schema exists and the query intent is already clear.

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 `from`/`to` formats, the `fields` subset enumeration, and the exact `lga_name` matching rule are all already documented in the schema. The description adds only a pointer to a fuller field list and method page, which is marginal but not harmful.

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?

States a specific question the tool answers (counts and share of Aboriginal/Torres Strait Islander residents) and names the geographic grain (suburb and council area). The 'for every suburb and council area' phrasing sits awkwardly against an `lga_name`-required schema and a sibling named suburbs_area_stats_indigenous_status, which muddies the resource scope slightly.

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 coverage paragraph and the prerequisite that `lga_name` must match `/v1/lga/list` output, which is genuinely useful. However, it never says when to pick this over the suburbs sibling or the non-Indigenous-status LGA datasets, leaving the agent to infer routing from the name 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