Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Taxpayers by income bracket by postcode

postcodes_economy_income_distribution
Read-onlyIdempotent

How many taxpayers in each postcode fall into each of five taxable-income brackets, per income year 2016-17 to 2023-24.

Coverage: About 2,530 postcodes; income years 2016-17 to 2023-24. Current to 2024-06-30. Full description, field list and method: /v1/datasets/income-distribution.

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": {
      "postcode": "<postcode>"
    },
    "name": "postcodes_economy_income_distribution"
  }
}

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: bracket_1, bracket_2, bracket_3, bracket_4, bracket_5. Omit for all.
postcodeYesFour-digit postcode, e.g. `2026`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 closed-world, so safety is covered. The description adds genuinely non-obvious behavior: a 5¢ per-call price, the ~2,530 postcode coverage limit, data currency to 2024-06-30, and a pointer to the full method/field documentation. It does not describe result shape or pagination, which keeps it from a 5.

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 metric is front-loaded in the first sentence, followed by coverage and cost, so an agent can decide quickly. There is minor redundancy in restating the income-year range twice and the pricing line is stylistically loud, but nothing is wasted.

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 should clarify what comes back; it says only that five brackets are reported and defers field lists and method to /v1/datasets/income-distribution. That pointer plus coverage and currency make it usable, but the response structure (counts, labels, period keys) remains unspecified. Adequate rather than complete for a dataset-query tool.

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 description coverage is 100%, including formats for from/to and the enumerable bracket fields, so the schema already carries parameter meaning. The description reinforces that there are five income brackets and gives the valid income-year span, which loosely constrains from/to, but adds no syntax or semantics beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 first sentence states a specific verb and resource: counts of taxpayers per postcode split across five taxable-income brackets, for stated income years. It is clearly distinguishable from siblings such as postcodes_economy_taxpayer_age or postcodes_economy_taxpayer_occupation. It stops short of explicitly naming which sibling to use for adjacent questions, keeping it at 4.

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 through the coverage statement (about 2,530 postcodes, income years 2016-17 to 2023-24, current to 2024-06-30), which tells an agent when the data is and isn't applicable. There is no explicit when-to-use or when-not-to-use guidance, and no alternatives named despite many closely related economy/demographic 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