Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Suburb · Ancestry breakdown

suburbs_ethnicity_ancestry
Read-onlyIdempotent

Ancestry breakdown: broad ancestry groups as fractions (0–1) of residents.

Price: 3¢ 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_ethnicity_ancestry"
  }
}

Input Schema

NameRequiredDescriptionDefault
suburb_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "available": {
-      "anyOf": [
-        {
-          "type": "boolean"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "`false` on no-data responses. Omitted on success — branch on `data !== null` if you want a single discriminator.",
-      "title": "Available"
-    },
-    "data": {
-      "anyOf": [
-        {
-          "items": {
-            "additionalProperties": true,
-            "description": "One row of ancestry / birthplace data.",
-            "example": {
-              "ancestry": "Australians",
-              "area_level": "suburb",
-              "area_name": "Belmont North",
-              "proportion": 0.926304347826087
-            },
-            "properties": {
-              "ancestry": {
-                "anyOf": [
-                  {
-                    "type": "string"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ],
-                "description": "Only on /ethnicity/ancestry.",
-                "title": "Ancestry"
-              },
-              "area_level": {
-                "description": "Always 'suburb'.",
-                "title": "Area Level",
-                "type": "string"
-              },
-              "area_name": {
-                "description": "Suburb (SAL) name.",
-                "title": "Area Name",
-                "type": "string"
-              },
-              "birthplace": {
-                "anyOf": [
-                  {
-                    "type": "string"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ],
-                "description": "Only on /ethnicity/birthplace.",
-                "title": "Birthplace"
-              },
-              "proportion": {
-                "anyOf": [
-                  {
-                    "type": "number"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ],
-                "description": "Share of the suburb identifying with this category (0–1).",
-                "title": "Proportion"
-              }
-            },
-            "required": [
-              "area_name",
-              "area_level"
-            ],
-            "title": "EthnicityRow",
-            "type": "object"
-          },
-          "type": "array"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "The endpoint's payload, or `null` when Microburbs has no value.",
-      "title": "Data"
-    },
-    "message": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "Human-readable explanation. Omitted on success.",
-      "title": "Message"
-    },
-    "reason": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "Machine-readable slug naming the no-data condition (e.g. `no_avm_for_GANSW704074813`). Stable per endpoint. Omitted on success.",
-      "title": "Reason"
-    }
-  },
-  "title": "ApiResponse[list[EthnicityRow]]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_list_EthnicityRow__"
-}New value: +null
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context by disclosing a 3¢ per-call price and stating that results are normalized fractions rather than counts, but it says nothing about coverage limits, how many groups are returned, or geography.

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 definition is two short lines, front-loading what the tool returns before the billing note. Every sentence carries information; the bolded price is a distinct concern but earns its place as a cost signal.

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 usefully specifies the value format (fractions 0–1) and the subject (residents). It remains incomplete about the shape of the response, the number or naming of ancestry groups, and the geographic scope, which matters given the cluster of similarly named ancestry tools.

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?

The tool has exactly one required parameter, so the zero-parameter baseline of 4 does not apply and schema coverage is 0%. The description never mentions suburb_name or what form it should take (suburb vs postcode, state disambiguation, matching behavior), leaving the single input entirely to inference, though for a one-parameter lookup this is a modest gap.

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 resource (ancestry breakdown), the granularity (broad ancestry groups), and the unit of the values (fractions 0–1 of residents), so an agent knows exactly what data comes back. It does not differentiate itself from close siblings such as suburbs_ethnicity_all, suburbs_ethnicity_birthplace, or suburbs_area_stats_ancestry, so an agent cannot infer the boundary between them from the text alone.

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 when-to-use guidance, no exclusion criteria, and no mention of any alternative tool. The only qualifier is the price line, which informs cost decisions but not selection between the many ancestry-related siblings.

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