Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

LGA · Education and qualifications

lga_area_stats_education
Read-onlyIdempotent

How far residents went at school and the highest qualification they hold since: Year 12 to Year 8 or below, and postgraduate, bachelor, diploma and certificate levels, for every suburb and council area.

Coverage: About 10,500 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/education.

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

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_left_school, year_12_count, year_12_pct, year_11_count, year_11_pct, year_10_count, year_10_pct, year_9_count, year_9_pct, year_8_or_below_count, year_8_or_below_pct, did_not_go_to_school_count, did_not_go_to_school_pct, school_not_stated_count, school_not_stated_pct, total_aged_15_plus, bachelor_or_higher_count, bachelor_or_higher_pct, postgraduate_degree_count, postgraduate_degree_pct, graduate_diploma_or_certificate_count, graduate_diploma_or_certificate_pct, bachelor_degree_count, bachelor_degree_pct, advanced_diploma_or_diploma_count, advanced_diploma_or_diploma_pct, certificate_count, certificate_pct, certificate_3_or_4_count, certificate_3_or_4_pct, certificate_1_or_2_count, certificate_1_or_2_pct, certificate_level_unspecified_count, certificate_level_unspecified_pct, qualification_inadequately_described_count, qualification_inadequately_described_pct, qualification_level_not_stated_count, qualification_level_not_stated_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 read-only, idempotent, closed-world, non-destructive behavior, so the bar is lower. The description adds genuinely useful non-schema context: a 5¢ per-call price, the exclusion of areas with too few people or dwellings for reliable figures, the single 10 August 2021 snapshot date, and a pointer to `/v1/datasets/education` for method and field details.

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 measure inventory is front-loaded, followed by coverage and documentation pointers, so an agent can grasp the tool from the first sentence. A minor redundancy appears in stating 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.

Completeness3/5

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

With no output schema, the description does useful work by listing the measure families that come back. However, it never reconciles the 'every suburb and council area' claim with a schema that only accepts `lga_name`, leaving a real risk that an agent attempts suburb-level queries here instead of using the suburbs sibling.

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 already documented in detail, which sets the baseline at 3. The description adds only indirect meaning, enumerating the qualification categories that correspond to the `fields` options, and says nothing extra about the from/to range syntax or the LGA-name matching rule.

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 the specific subject matter (school attainment and highest qualification, from Year 12 down to Year 8 or below, plus postgraduate/bachelor/diploma/certificate levels) and ties it to a specific geographic level via the dataset link. It stops short of distinguishing this LGA tool from the sibling `suburbs_area_stats_education`, and the phrase 'for every suburb and council area' works against the LGA-only `lga_name` parameter.

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?

There is no explicit statement of when to use this tool versus the suburbs variant or the many other `lga_area_stats_*` siblings. The coverage note does imply usage context (Australian LGA-level education statistics, one 2021 snapshot), but the agent must infer selection criteria from the tool name alone.

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