Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Suburb · Religion

suburbs_area_stats_religion
Read-onlyIdempotent

How many residents follow each religion, and what share of the area that is: 30 groups from Anglican to Sikh to no religion, 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 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/religion.

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_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: total_population, christianity_count, christianity_pct, anglican_count, anglican_pct, baptist_count, baptist_pct, brethren_count, brethren_pct, catholic_count, catholic_pct, churches_of_christ_count, churches_of_christ_pct, eastern_orthodox_count, eastern_orthodox_pct, jehovahs_witnesses_count, jehovahs_witnesses_pct, latter_day_saints_count, latter_day_saints_pct, lutheran_count, lutheran_pct, oriental_orthodox_count, oriental_orthodox_pct, other_christian_count, other_christian_pct, other_protestant_count, other_protestant_pct, pentecostal_count, pentecostal_pct, presbyterian_reformed_count, presbyterian_reformed_pct, salvation_army_count, salvation_army_pct, seventh_day_adventist_count, seventh_day_adventist_pct, uniting_church_count, uniting_church_pct, assyrian_apostolic_count, assyrian_apostolic_pct, christian_unspecified_count, christian_unspecified_pct, buddhism_count, buddhism_pct, hinduism_count, hinduism_pct, islam_count, islam_pct, judaism_count, judaism_pct, sikhism_count, sikhism_pct, aboriginal_traditional_count, aboriginal_traditional_pct, other_religious_groups_count, other_religious_groups_pct, other_religions_count, other_religions_pct, no_religion_count, no_religion_pct, secular_beliefs_count, secular_beliefs_pct, other_spiritual_beliefs_count, other_spiritual_beliefs_pct, no_religion_or_secular_count, no_religion_or_secular_pct, not_stated_count, 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.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, and the description adds genuinely new context: ~11,000 suburbs and 545 council areas, exclusion of low-population areas, a single 2021-08-10 snapshot, and a 5¢ per-call price. It notably clarifies that only one time point exists despite the from/to parameters, though it does not describe response shape or result limits.

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?

Front-loaded with the core question and answerable fields, then a clearly separated coverage/price block. Minor waste in restating the snapshot date twice ('one snapshot at 10 August 2021' and 'Current to 2021-08-10').

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 stats tool with a fully documented schema and no output schema, the description supplies the coverage scope, temporal snapshot, exclusions, cost, and a pointer to full documentation. The remaining gap is sibling routing—nothing explains why to pick this over lga_area_stats_religion—but nothing required to call the tool is missing.

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 the schema already documents from/to formats, the full fields list, and the suburb_name format with an example. The description adds only a conceptual gloss ('how many' vs 'what share' mapping to count/pct) and the note that a single snapshot exists; it adds no new parameter-level guidance beyond that.

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 measurement (resident counts and percentage shares by religion, 30 groups) and the geographic unit, so the resource is unambiguous. The one weakness is that it claims coverage 'for every suburb and council area' even though a sibling named lga_area_stats_religion exists, leaving the suburb-vs-LGA split slightly blurred.

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 topic (religion breakdowns per area) but there is no explicit when-to-use statement, no mention of when to prefer lga_area_stats_religion or suburbs_area_stats_income_by_religion, and no note that the area name must be resolved via /v1/suburbs/list first (that only appears in the schema).

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