Skip to main content
Glama

Microburbs Australian Property Data

Suburb · Places of worship and community centres

suburbs_amenities_community_and_worship
Read-onlyIdempotent

Christian churches, mosques, Hindu, Buddhist and Sikh temples, synagogues, community centres and halls, and cemeteries: counts in the suburb, rates per 1,000 residents and distance from the suburb centre to the nearest of each.

Coverage: All Australian suburbs and localities. Current to 2026-10-01. Full description, field list and method: /v1/datasets/community-and-worship.

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

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: count_churches, per_1000_churches, nearest_km_churches, count_mosques, per_1000_mosques, nearest_km_mosques, count_hindu_temples, per_1000_hindu_temples, nearest_km_hindu_temples, count_buddhist_temples, per_1000_buddhist_temples, nearest_km_buddhist_temples, count_sikh_temples, per_1000_sikh_temples, nearest_km_sikh_temples, count_synagogues, per_1000_synagogues, nearest_km_synagogues, count_community_centres, per_1000_community_centres, nearest_km_community_centres, count_cemeteries, per_1000_cemeteries, nearest_km_cemeteries, count_total, per_1000_total, per_km2_total. 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

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds context the annotations cannot carry: the per-call price (5¢), the currency of the dataset, and a pointer to the full method/field documentation. It stops short of describing response shape or behaviour for suburbs with no matching places, which is the remaining 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?

Content is front-loaded: the resource and metric scope arrive in the first sentence, then coverage, then documentation, then price. Nothing is filler. Minor deduction for the fragmented four-block layout, where the standalone price line breaks the flow of the otherwise tight opening.

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-required-parameter dataset query with no output schema, the definition supplies what an agent needs: scope, coverage, currency, cost, and a link to field/method detail. The absence of return-format or pagination information is the only notable shortfall, and it is mitigated by the documentation pointer.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the prose earns a bump by explaining what the metric families mean in practice — `per_1000_*` is a rate per 1,000 residents and `nearest_km_*` is distance from the suburb centre to the nearest instance — which the terse comma-separated field list does not spell out. It adds no detail on disjointness of `fields` or how the period window maps to the returned rows.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific resource categories (churches, mosques, Hindu/Buddhist/Sikh temples, synagogues, community centres, halls, cemeteries) and the three metric families returned: counts in the suburb, rates per 1,000 residents, and distance from the suburb centre to the nearest of each. That is enough to distinguish it from the other amenity siblings such as education_and_childcare or parks_and_recreation without opening any schema.

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

Usage Guidelines4/5

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

Coverage is stated explicitly (all Australian suburbs and localities, current to 2026-10-01) and the category enumeration implicitly tells the agent which sibling to pick for a different amenity type. What is missing is explicit routing language for when to use this versus a neighbouring tool, and any guidance on how the `from`/`to` window should be chosen.

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