Skip to main content
Glama

Microburbs Australian Property Data

Suburb · Income by religion

suburbs_area_stats_income_by_religion
Read-onlyIdempotent

How much each religious group earns: weekly personal income bands for seven religion groups, in every suburb and council area.

Coverage: About 11,300 suburbs and localities and 545 council areas across Australia, in all states and territories (areas with too few residents 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/income-by-religion.

Price: 10¢ 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_income_by_religion"
  }
}

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: all_income_stated, all_under_500_pct, all_500_to_999_pct, all_1000_to_1999_pct, all_2000_plus_pct, buddhism_income_stated, buddhism_under_500_count, buddhism_under_500_pct, buddhism_500_to_999_count, buddhism_500_to_999_pct, buddhism_1000_to_1999_count, buddhism_1000_to_1999_pct, buddhism_2000_plus_count, buddhism_2000_plus_pct, christianity_income_stated, christianity_under_500_count, christianity_under_500_pct, christianity_500_to_999_count, christianity_500_to_999_pct, christianity_1000_to_1999_count, christianity_1000_to_1999_pct, christianity_2000_plus_count, christianity_2000_plus_pct, hinduism_income_stated, hinduism_under_500_count, hinduism_under_500_pct, hinduism_500_to_999_count, hinduism_500_to_999_pct, hinduism_1000_to_1999_count, hinduism_1000_to_1999_pct, hinduism_2000_plus_count, hinduism_2000_plus_pct, islam_income_stated, islam_under_500_count, islam_under_500_pct, islam_500_to_999_count, islam_500_to_999_pct, islam_1000_to_1999_count, islam_1000_to_1999_pct, islam_2000_plus_count, islam_2000_plus_pct, judaism_income_stated, judaism_under_500_count, judaism_under_500_pct, judaism_500_to_999_count, judaism_500_to_999_pct, judaism_1000_to_1999_count, judaism_1000_to_1999_pct, judaism_2000_plus_count, judaism_2000_plus_pct, other_religions_income_stated, other_religions_under_500_count, other_religions_under_500_pct, other_religions_500_to_999_count, other_religions_500_to_999_pct, other_religions_1000_to_1999_count, other_religions_1000_to_1999_pct, other_religions_2000_plus_count, other_religions_2000_plus_pct, no_religion_income_stated, no_religion_under_500_count, no_religion_under_500_pct, no_religion_500_to_999_count, no_religion_500_to_999_pct, no_religion_1000_to_1999_count, no_religion_1000_to_1999_pct, no_religion_2000_plus_count, no_religion_2000_plus_pct, buddhism_share_of_top_earners_pct, christianity_share_of_top_earners_pct, hinduism_share_of_top_earners_pct, islam_share_of_top_earners_pct, judaism_share_of_top_earners_pct, other_religions_share_of_top_earners_pct, no_religion_share_of_top_earners_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.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds genuinely non-structured facts: ~11,300 suburbs and 545 council areas covered, areas with too few residents excluded (explaining empty results), a single 2021-08-10 snapshot, and a 10¢ per-call price. It stops short of saying what the response rows look like, but the coverage, recency and cost disclosures are the valuable additions here.

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 core measure is front-loaded in the first clause, then coverage, snapshot date, documentation pointer and price in descending importance. Minor redundancy: 'one snapshot at 10 August 2021' and 'Current to 2021-08-10' state the same fact twice.

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 read-only single-dataset lookup with a fully documented schema, the description supplies what matters: scope, exclusion rule for unreliably small areas, vintage, price, and a link to the full field list and method. The remaining gap is the unresolved suburb-vs-LGA query boundary shared with its sibling tool.

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%, including a peer-format hint on `from`/`to` and the exact enum-like field list, so the baseline is 3. The description adds only the framing that fields are income bands across seven religion groups, which helps an agent choose `fields` but does not add syntax or constraints beyond the schema.

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 a specific measure (weekly personal income bands by religion group) and its geographic scope (every suburb and council area), so an agent can tell what data it returns. It does not distinguish itself from the near-identical sibling lga_area_stats_income_by_religion, and by claiming 'every suburb and council area' it actively blurs the boundary with that LGA-scoped tool.

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 geographic scope statement but never stated explicitly — there is no 'use this when…' clause and no named alternative for council-level lookups or for the non-income religion sibling (suburbs_area_stats_religion). The note that small-population areas are omitted is useful context but is a coverage caveat, not usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources