suburbs_market_rent_mapMedian advertised weekly house rent for every microburb (mesh block) in
the suburb, with its modal street name, plus the dearest and cheapest
pockets. Values only — the matching polygons come from
/shapes/mesh-blocks.
| 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 weekly rent — the report's `rent` overlay.",
- "example": {
- "as_of": "2026-08-16",
- "definition": "Modelled median (50th-percentile) advertised weekly rent for a house in the mesh block. Mesh block = 'microburb', the smallest ABS geography (~30-60 dwellings). Microburbs with too little rental signal are absent rather than zero. Compare the suburb-wide figure at /market/median-rent.",
- "highest": {
- "mb": "10439020000",
- "street": "Floraville",
- "weekly_rent": 1140
- },
- "lowest": {
- "mb": "10434270000",
- "street": "Somerset",
- "weekly_rent": 519
- },
- "metric": "median_weekly_rent_house",
- "microburbs": [
- {
- "mb": "10439020000",
- "street": "Floraville",
- "weekly_rent": 1140
- }
- ],
- "n_microburbs": 58,
- "suburb": "Belmont North",
- "unit": "AUD_per_week"
- },
- "properties": {
- "as_of": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Date of the rent surface (YYYY-MM-DD).",
- "title": "As Of"
- },
- "definition": {
- "description": "How the figure is derived.",
- "title": "Definition",
- "type": "string"
- },
- "highest": {
- "anyOf": [
- {
- "additionalProperties": true,
- "description": "Median weekly house rent for one microburb (mesh block).",
- "properties": {
- "mb": {
- "description": "ABS 2021 mesh-block code.",
- "title": "Mb",
- "type": "string"
- },
- "street": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Modal street name for the mesh block, title-cased.",
- "title": "Street"
- },
- "weekly_rent": {
- "description": "Median advertised weekly house rent, AUD.",
- "title": "Weekly Rent",
- "type": "integer"
- }
- },
- "required": [
- "mb",
- "weekly_rent"
- ],
- "title": "RentMb",
- "type": "object"
- },
- {
- "type": "null"
- }
- ],
- "description": "Dearest microburb. None when there is no spread."
- },
- "lowest": {
- "anyOf": [
- {
- "additionalProperties": true,
- "description": "Median weekly house rent for one microburb (mesh block).",
- "properties": {
- "mb": {
- "description": "ABS 2021 mesh-block code.",
- "title": "Mb",
- "type": "string"
- },
- "street": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Modal street name for the mesh block, title-cased.",
- "title": "Street"
- },
- "weekly_rent": {
- "description": "Median advertised weekly house rent, AUD.",
- "title": "Weekly Rent",
- "type": "integer"
- }
- },
- "required": [
- "mb",
- "weekly_rent"
- ],
- "title": "RentMb",
- "type": "object"
- },
- {
- "type": "null"
- }
- ],
- "description": "Cheapest microburb. None when there is no spread."
- },
- "metric": {
- "description": "Always 'median_weekly_rent_house'.",
- "title": "Metric",
- "type": "string"
- },
- "microburbs": {
- "description": "Per-microburb rents, dearest first.",
- "items": {
- "additionalProperties": true,
- "description": "Median weekly house rent for one microburb (mesh block).",
- "properties": {
- "mb": {
- "description": "ABS 2021 mesh-block code.",
- "title": "Mb",
- "type": "string"
- },
- "street": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Modal street name for the mesh block, title-cased.",
- "title": "Street"
- },
- "weekly_rent": {
- "description": "Median advertised weekly house rent, AUD.",
- "title": "Weekly Rent",
- "type": "integer"
- }
- },
- "required": [
- "mb",
- "weekly_rent"
- ],
- "title": "RentMb",
- "type": "object"
- },
- "title": "Microburbs",
- "type": "array"
- },
- "n_microburbs": {
- "description": "Microburbs with a rent.",
- "title": "N Microburbs",
- "type": "integer"
- },
- "suburb": {
- "description": "Canonical SAL name.",
- "title": "Suburb",
- "type": "string"
- },
- "unit": {
- "description": "Always 'AUD_per_week'.",
- "title": "Unit",
- "type": "string"
- }
- },
- "required": [
- "suburb",
- "metric",
- "unit",
- "definition",
- "n_microburbs",
- "microburbs"
- ],
- "title": "SuburbRentMap",
- "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[SuburbRentMap]",
- "type": "object",
- "x-fastmcp-top-level-schema": "ApiResponse_SuburbRentMap_"
-}New value: +nullDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context that the tool returns values only and that matching polygons must be fetched from /shapes/mesh-blocks, which clarifies a key behavioral boundary. It doesn't disclose response format or pagination, but with annotations covering safety, this is adequate.
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?
The description is compact and front-loaded with the core metric, then adds the modal street name and dearest/cheapest pockets, and ends with a useful pointer to the shapes endpoint. Every sentence earns its place, though the final sentence could be seen as slightly tangential to the tool's own invocation.
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?
For a simple one-parameter read-only tool, the description covers the main output and the key dependency on the shapes endpoint. However, it doesn't mention what the response structure looks like, whether the result is a single value or a list, or any units beyond 'weekly rent'. Given no output schema, a bit more detail on return shape would improve completeness.
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?
Schema description coverage is 0%, so the description carries the burden for the single parameter. The description names the resource (suburb) and implies suburb_name is the input, but it doesn't specify format, case sensitivity, or whether full names or codes are accepted. Since there is only one parameter and the tool name plus description make its purpose clear, a baseline 3 is appropriate.
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 the tool returns median advertised weekly house rent per microburb, with modal street name and dearest/cheapest pockets. It identifies the resource (suburb) and the specific metric, but doesn't explicitly differentiate it from the many other suburbs_market_* siblings beyond the microburb/mesh block focus.
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 usage for rent values per microburb and notes that polygons come from a separate shapes endpoint, which is useful routing guidance. However, it doesn't explicitly state when to choose this over alternatives like suburbs_market_median_rent or suburbs_market_vacancy_map, nor does it mention any exclusions.
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.