Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Suburb · Australian citizenship

suburbs_area_stats_citizenship
Read-onlyIdempotent

How many residents are Australian citizens, 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/citizenship.

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

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, australian_citizens_count, australian_citizens_pct, not_citizen_or_not_stated_count, not_citizen_or_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 declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context: the 2021-08-10 snapshot vintage, the exclusion of areas with too few people or homes, and a per-call price of 5¢, which matters for an agent deciding whether to call repeatedly. It stops short of describing the response shape or pagination.

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?

Purpose is front-loaded, then coverage, then docs pointer, then price — a sensible order with little waste. The only redundancy is 'one snapshot at 10 August 2021' immediately followed by 'Current to 2021-08-10', which restates 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 four-parameter, single-metric lookup with full schema coverage and annotations, the definition supplies coverage, vintage, method pointer and cost. With no output schema, a one-line note on return shape would have closed the last 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%, with each of the four parameters documented, including the `fields` enum and the `from`/`to` formats, so the baseline is 3. The description adds nothing parameter-specific beyond the field-name list already in 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?

States a concrete question the tool answers ('How many residents are Australian citizens, and what share of the area') and the grain ('for every suburb and council area'), which is more specific than the name alone. It does not, however, distinguish itself from the sibling lga_area_stats_citizenship, even though the stated scope explicitly covers council areas.

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 note (11,000 suburbs, 545 council areas, small areas excluded) and the pointer to `/v1/datasets/citizenship`, but there is no explicit when-to-use or when-not-to-use statement. An agent must infer from the sibling name that lga_area_stats_citizenship is the narrower alternative.

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