suburbs_demographics_income_mapMedian weekly household income for every microburb in the suburb, plus the suburb median, national percentile and highest/lowest pockets.
| Name | Required | Description | Default |
|---|---|---|---|
| suburb_name | Yes |
Changes observed during successful MCP inspections.
Output 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": [
- {
- "additionalProperties": true,
- "description": "Per-microburb median household income map.",
- "example": {
- "highest": {
- "street": "Marquis St",
- "weekly_income": 2105
- },
- "lowest": {
- "street": "Kalaroo Rd",
- "weekly_income": 1188
- },
- "median_weekly_income": 1740,
- "microburbs": [
- {
- "mb": "10664530000",
- "street": "Marquis St",
- "weekly_income": 2105
- }
- ],
- "n_microburbs": 71,
- "national_percentile": 55,
- "suburb": "Belmont North"
- },
- "properties": {
- "highest": {
- "anyOf": [
- {
- "additionalProperties": true,
- "description": "Highest/lowest income pocket callout.",
- "properties": {
- "street": {
- "description": "Modal street of the pocket's MB.",
- "title": "Street",
- "type": "string"
- },
- "weekly_income": {
- "description": "Median household income ($/week).",
- "title": "Weekly Income",
- "type": "integer"
- }
- },
- "required": [
- "street",
- "weekly_income"
- ],
- "title": "IncomePocket",
- "type": "object"
- },
- {
- "type": "null"
- }
- ],
- "description": "Highest-income pocket."
- },
- "lowest": {
- "anyOf": [
- {
- "additionalProperties": true,
- "description": "Highest/lowest income pocket callout.",
- "properties": {
- "street": {
- "description": "Modal street of the pocket's MB.",
- "title": "Street",
- "type": "string"
- },
- "weekly_income": {
- "description": "Median household income ($/week).",
- "title": "Weekly Income",
- "type": "integer"
- }
- },
- "required": [
- "street",
- "weekly_income"
- ],
- "title": "IncomePocket",
- "type": "object"
- },
- {
- "type": "null"
- }
- ],
- "description": "Lowest-income pocket."
- },
- "median_weekly_income": {
- "anyOf": [
- {
- "type": "integer"
- },
- {
- "type": "null"
- }
- ],
- "description": "Suburb median household income ($/week).",
- "title": "Median Weekly Income"
- },
- "microburbs": {
- "description": "Per-microburb incomes.",
- "items": {
- "additionalProperties": true,
- "description": "One microburb's median weekly household income.",
- "properties": {
- "mb": {
- "description": "ABS mesh-block code.",
- "title": "Mb",
- "type": "string"
- },
- "street": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Modal street name in the MB.",
- "title": "Street"
- },
- "weekly_income": {
- "description": "Median household income ($/week).",
- "title": "Weekly Income",
- "type": "integer"
- }
- },
- "required": [
- "mb",
- "weekly_income"
- ],
- "title": "IncomeMb",
- "type": "object"
- },
- "title": "Microburbs",
- "type": "array"
- },
- "n_microburbs": {
- "description": "Microburbs with income data.",
- "title": "N Microburbs",
- "type": "integer"
- },
- "national_percentile": {
- "anyOf": [
- {
- "type": "integer"
- },
- {
- "type": "null"
- }
- ],
- "description": "National income percentile, clamped 1-99.",
- "title": "National Percentile"
- },
- "suburb": {
- "description": "Canonical SAL name.",
- "title": "Suburb",
- "type": "string"
- }
- },
- "required": [
- "suburb",
- "n_microburbs",
- "microburbs"
- ],
- "title": "SuburbIncomeMap",
- "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[SuburbIncomeMap]",
- "type": "object",
- "x-fastmcp-top-level-schema": "ApiResponse_SuburbIncomeMap_"
-}New value: +nullDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the read-only, idempotent, and non-destructive profile, so the description doesn't need to restate safety. It adds useful output content, such as the national percentile and extreme pockets, but does not disclose response format, data source, or any operational details. This is adequate but not rich behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One sentence, front-loaded with the primary metric, followed by the supplementary statistics. There is no filler or repetition, and every phrase earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With one simple required parameter, no output schema, and read-only annotations, the description conveys enough return content for an agent to call the tool and interpret results. Minor gaps such as exact map/table structure or response format prevent a 5.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There is a single required string parameter with no schema description, and the phrase 'in the suburb' lightly confirms that suburb_name is the lookup value. The parameter is fairly self-explanatory, but because schema coverage is 0%, the description only partially compensates and provides no guidance on valid suburb name formats.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states what the tool returns: median weekly household income for every microburb, plus the suburb median, national percentile, and highest/lowest pockets. The 'microburb' granularity and 'pockets' wording distinguish it from the adjacent suburbs_demographics_income tool. It lacks a 5 only because it doesn't explicitly contrast itself with that sibling.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use the tool: whenever microburb-level household income data is needed. It offers no explicit when-not-to-use guidance and names no alternative tool, so an agent must infer the right context from the metric and the title.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.