Microburbs Australian Property Data

Property · All basics — bundle

properties_basics_all

Read-onlyIdempotent

Price: 23¢ per call.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`gnaf_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 15, 2026

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": "All property basics — beds, baths, parking, dwelling type, land area —\nin one call.\n\nEvery one of these comes from what the property was advertised with, so\na null is \"never advertised\" rather than \"zero\", and a property that has\nnever been listed comes back with all five null. Values are returned\nflat here (no per-field wrapper object, unlike the individual endpoints).",
-          "example": {
-            "bath_count": 2,
-            "bed_count": 4,
-            "dwelling_type": "house",
-            "land_area_sqm": 814,
-            "parking_count": 5
-          },
-          "properties": {
-            "bath_count": {
-              "anyOf": [
-                {
-                  "type": "integer"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Bathrooms as advertised, whole number. Null = unknown, not zero.",
-              "title": "Bath Count"
-            },
-            "bed_count": {
-              "anyOf": [
-                {
-                  "type": "integer"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Bedrooms as advertised. Null = unknown, not zero.",
-              "title": "Bed Count"
-            },
-            "dwelling_type": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Dwelling kind in lowercase free text ('house', 'unit', 'townhouse', …), from the listing or the national address file. Not a closed set.",
-              "title": "Dwelling Type"
-            },
-            "land_area_sqm": {
-              "anyOf": [
-                {
-                  "type": "number"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Advertised land size in square metres (hectares converted for you), indicative rather than surveyed. Null = not stated; usual for units.",
-              "title": "Land Area Sqm"
-            },
-            "parking_count": {
-              "anyOf": [
-                {
-                  "type": "integer"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Covered car spaces (garage/carport) as advertised — excludes open driveway and street parking. Null = unknown.",
-              "title": "Parking Count"
-            }
-          },
-          "title": "BasicsAll",
-          "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[BasicsAll]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_BasicsAll_"
-}New value: +null

First observedSep 14, 2026

TDQS

D1.5/5.0

Behavior1/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the bar for additional disclosure is lower; even so, the description contributes zero behavioral context beyond the price. Pricing is not a behavioral trait.

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

Conciseness2/5

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

The description is short but not concise in a useful way: the single sentence is spent on price rather than tool behavior, so this is under-specification rather than well-structured completeness.

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

Completeness1/5

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

For a tool with one required parameter, no output schema, and many closely related sibling endpoints, the description is severely incomplete. Nothing in the description tells the agent what data will be returned or how this bundled call relates to the individual properties_basics_* tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description does not mention gnaf_id or explain what value to pass or what its format is. The parameter name is suggestive, but the description itself adds no semantic meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description text is only '**Price: 23¢ per call.**' – it never states what action the tool performs or what 'all basics' includes. The name and title hint at a bundle of basic property attributes for a G-NAF ID, but that is inference, not a stated purpose.

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?

No when-to-use guidance is given, and no alternatives are mentioned despite an extensive sibling set including properties_basics_bath_count, properties_basics_bed_count, properties_basics_dwelling_type, etc. An agent cannot determine whether to call this bundle or a specific basics endpoint.

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 tools Inspect

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

Need Help?