Skip to main content
Glama

Microburbs Australian Property Data

Suburb · Childcare and early learning

suburbs_amenities_education_and_childcare
Read-onlyIdempotent

Childcare centres and preschools or kindergartens (schools are served separately): 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/education-and-childcare.

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

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_childcare, per_1000_childcare, nearest_km_childcare, count_preschools, per_1000_preschools, nearest_km_preschools, 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.1/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 openWorld=false, so the safety profile is covered. The description adds genuinely useful context beyond that: per-call cost (5¢), data currency (current to 2026-10-01), geographic coverage, and a pointer to the method/field documentation. It does not say how invalid or ambiguous suburb names are handled, which is the main residual behavioral 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?

Front-loaded with the substantive content (what is counted and in what units) before the coverage/currency line, the documentation pointer, and the price. Every sentence carries information; the only mild redundancy is restating the title's domain in the opening clause.

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?

With no output schema and four well-documented parameters, the description supplies what an agent still needs: metric semantics, units, geography, freshness, cost, and where the field list lives. Period-selection semantics for from/to are left entirely to the schema, which covers them adequately, so nothing critical is missing.

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 coverage is 100%, so the baseline is 3. The description improves on that by explaining what the measures actually mean — that counts are for the suburb, rates are per 1,000 residents, and distances are from the suburb centre to the nearest facility — which gives semantic content to fields like nearest_km_childcare and per_1000_preschools that the schema only names.

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 states a specific resource (childcare centres and preschools/kindergartens) and the exact measures returned (counts in the suburb, rates per 1,000 residents, distance from the suburb centre to the nearest of each). It explicitly carves out schools as served elsewhere, so an agent can separate it from the education/schools siblings without opening a schema.

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 rather than stated: the 'schools are served separately' note routes one adjacent case away, and the coverage line tells the agent the data applies to all Australian suburbs. There is no explicit statement of when to prefer this over area-stats or nearby-properties tools, and no named alternative.

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