Skip to main content
Glama

Microburbs Australian Property Data

LGA · Income by religion

lga_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": {
      "lga_name": "<lga_name>"
    },
    "name": "lga_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.
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

B3.4/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 safety profile is covered. The description adds genuinely new behavioral facts: a 10¢ per-call price, a fixed 10 August 2021 snapshot, and the exclusion of areas with too few residents for reliable figures — the latter matters because it explains silently missing rows. It does not describe pagination or response shape, but with no output schema that is a minor gap.

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?

Three short blocks with the substantive purpose front-loaded, followed by coverage and then the price. Nothing is padded, and the doc link plus cost line are operational facts worth their space. The only wasted wording is the 'suburb and council area' phrasing that implies broader scope than the schema allows.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only data query tool with a fully described schema, the description covers what the data measures, its vintage, its coverage limits and its cost. What is missing is the scope boundary that matters most: that this returns LGA-level rows only and that suburb-level figures come from the sibling tool. That omission, plus silence on how from/to behave against a single snapshot, leaves a real gap.

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 from/to, fields and lga_name are all documented inline, including the full field list and the lga_name format reference. The description contributes only the concept of 'seven religion groups' and income bands, which the field list already encodes. It does not clarify that from/to operate over a single-snapshot dataset, which would have been useful added meaning.

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 verb and resource: weekly personal income bands broken down by seven religion groups. That is concrete and distinguishable from siblings like lga_area_stats_religion or lga_area_stats_income_by_birthplace. However, the phrase 'in every suburb and council area' misdescribes this tool's actual scope, since lga_name is required and only LGA rows are returned — the suburbs variant is a separate sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance and no explicit routing to alternatives such as suburbs_area_stats_income_by_religion for suburb-level data or lga_area_stats_religion for overall religious affiliation counts. The coverage sentence implies geographic scope but describes the dataset, not when to pick this tool over the LGA-versus-suburb variants. The one operational hint is that lga_name must match /v1/lga/list, which is prerequisite information rather than 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