Skip to main content
Glama

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Area Statistics · Search area-statistics fields

area_stats_fields
Read-onlyIdempotent

Discover which statistical fields exist. Free (0c). Fuzzy, token-based matching covers table topics and clean column labels as well as terse field codes. Common natural-language plurals and Census synonyms are handled, so the verbatim query=couples with children discovers the exact 2021 ABS family-composition count fields rather than substituting the broader census_family_households metric. Use the returned field code(s) with the priced /area-stats/SAL/{suburb}/values route. ~17k fields available.

Free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax fields to return.
queryNoFuzzy search over ABS field names/codes, table topics and column labels (e.g. 'total population', 'couple family children', 'tenure owned outright', or 'median rent'). Omit to list.

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": [
-        {
-          "description": "A page of matching fields.",
-          "example": {
-            "count": 1,
-            "fields": [
-              {
-                "field_code": "Median_rent_weekly",
-                "field_name": "Median rent weekly",
-                "label": "Median rent ($/weekly)",
-                "topic": "Selected Medians and Averages"
-              }
-            ]
-          },
-          "properties": {
-            "count": {
-              "description": "Number of fields returned.",
-              "title": "Count",
-              "type": "integer"
-            },
-            "fields": {
-              "description": "Matching fields, best match first.",
-              "items": {
-                "additionalProperties": true,
-                "description": "One statistical field in the catalog.",
-                "properties": {
-                  "field_code": {
-                    "description": "Stable field identifier — pass this to /values (e.g. 'Median_rent_weekly').",
-                    "title": "Field Code",
-                    "type": "string"
-                  },
-                  "field_name": {
-                    "description": "Human-readable field name (e.g. 'Median rent weekly').",
-                    "title": "Field Name",
-                    "type": "string"
-                  },
-                  "label": {
-                    "anyOf": [
-                      {
-                        "type": "string"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Clean column label for the field (e.g. 'Couple family with no children').",
-                    "title": "Label"
-                  },
-                  "topic": {
-                    "anyOf": [
-                      {
-                        "type": "string"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Subject of the source table — the context for cross-tab fields (e.g. 'Mortgage Repayment (Monthly) by Family Composition').",
-                    "title": "Topic"
-                  }
-                },
-                "required": [
-                  "field_code",
-                  "field_name"
-                ],
-                "title": "AreaStatField",
-                "type": "object"
-              },
-              "title": "Fields",
-              "type": "array"
-            }
-          },
-          "required": [
-            "count",
-            "fields"
-          ],
-          "title": "AreaStatFieldsResponse",
-          "type": "object"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "The endpoint's payload, or `null` when Microburbs has no value."
-    },
-    "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[AreaStatFieldsResponse]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_AreaStatFieldsResponse_"
-}New value: +null
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds significant value by disclosing that it is free, uses fuzzy token-based matching, handles plurals and Census synonyms, and covers ~17k fields. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is detailed but efficient, front-loading the core purpose, then providing matching details, an example, and usage direction. Every sentence earns its place without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

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

For a simple search tool with no output schema, the description covers what it does, how to use results, pricing, matching nuances, and scale. An agent has everything needed to call it correctly.

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% (both `limit` and `query` have descriptions). The description adds extra meaning by explaining that `query` performs fuzzy matching over field names/codes/topics/labels and gives concrete examples. It does not add much about `limit` but the schema covers it, so this is above baseline.

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 clearly states the tool discovers statistical fields via fuzzy search over ABS field names, codes, table topics, and column labels. It differentiates itself from the sibling `area_stats_values` by explicitly directing the agent to use returned codes with that route, making its purpose distinct.

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

Usage Guidelines5/5

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

The description provides explicit usage guidance: it is free, used for discovery, and the returned codes feed into the priced `/area-stats/SAL/{suburb}/values` route. It also explains the fuzzy matching behavior and synonym handling, so the agent knows when to prefer this over other tools.

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