Microburbs Australian Property Data

Suburb · Development Applications — bundle

suburbs_development_all

Read-onlyIdempotent

Shown in the suburb report as the 'Development Applications' card in the Development section.

What is being built in the suburb: the count of development applications on record, and the list itself with each application's address, type and status.

Read it as supply coming down the pipeline, and as a signal of where a suburb is changing.

Price: 24¢ 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": {
      "suburb_name": "<suburb_name>"
    },
    "name": "suburbs_development_all"
  }
}

Input Schema

Name	Required	Description	Default
`suburb_name`	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": [
-        {
-          "example": {
-            "da_count": 0,
-            "da_list": [
-              {
-                "area_level": "address",
-                "area_name": "",
-                "category": "Renovation",
-                "date": "2026-04-15",
-                "description": "Alterations and additions to existing dwelling.",
-                "suburb": "Belmont North"
-              }
-            ]
-          },
-          "properties": {
-            "da_count": {
-              "anyOf": [
-                {
-                  "type": "integer"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "title": "Da Count"
-            },
-            "da_list": {
-              "anyOf": [
-                {
-                  "items": {
-                    "additionalProperties": true,
-                    "description": "One development-application record near the suburb.",
-                    "properties": {
-                      "area_level": {
-                        "description": "'suburb' or 'address'.",
-                        "title": "Area Level",
-                        "type": "string"
-                      },
-                      "area_name": {
-                        "anyOf": [
-                          {
-                            "type": "string"
-                          },
-                          {
-                            "type": "null"
-                          }
-                        ],
-                        "description": "Suburb (SAL) name — may be empty for per-address rows.",
-                        "title": "Area Name"
-                      },
-                      "category": {
-                        "anyOf": [
-                          {
-                            "type": "string"
-                          },
-                          {
-                            "type": "null"
-                          }
-                        ],
-                        "description": "Coarse category — 'Renovation', 'New Dwelling', etc.",
-                        "title": "Category"
-                      },
-                      "date": {
-                        "anyOf": [
-                          {
-                            "type": "string"
-                          },
-                          {
-                            "type": "null"
-                          }
-                        ],
-                        "description": "DA lodged date (YYYY-MM-DD).",
-                        "title": "Date"
-                      },
-                      "description": {
-                        "anyOf": [
-                          {
-                            "type": "string"
-                          },
-                          {
-                            "type": "null"
-                          }
-                        ],
-                        "description": "Free-text description of the proposed works.",
-                        "title": "Description"
-                      },
-                      "suburb": {
-                        "anyOf": [
-                          {
-                            "type": "string"
-                          },
-                          {
-                            "type": "null"
-                          }
-                        ],
-                        "description": "Suburb the DA is in (when area_level=='address').",
-                        "title": "Suburb"
-                      }
-                    },
-                    "required": [
-                      "area_level"
-                    ],
-                    "title": "DaRow",
-                    "type": "object"
-                  },
-                  "type": "array"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "title": "Da List"
-            }
-          },
-          "title": "SuburbPlanningAll",
-          "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[SuburbPlanningAll]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_SuburbPlanningAll_"
-}New value: +null

First observedSep 14, 2026

TDQS

B3.2/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-structured context: the exact contents returned (count plus per-application address, type, status) and a per-call cost of 24¢, which matters for a bundled paid call. It stops short of stating auth requirements or whether a missing suburb errors or returns empty.

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 card identity is front-loaded, followed by payload contents, interpretive framing, and cost – a sensible order. The 'Read it as supply coming down the pipeline' sentence is interpretive padding rather than operational information, which is the only real waste.

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?

For a single-parameter read tool with no output schema, the description does well to describe the return shape and cost. The two gaps that matter – the undocumented suburb_name parameter and the lack of differentiation from the da_count/da_list/applications siblings – keep it at merely adequate.

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

Parameters2/5

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

There is a single required parameter, suburb_name, at 0% schema description coverage, so the description carries the full burden – and it never mentions the parameter. The subtitle 'in the suburb' only weakly implies that scope. No format, matching behavior (exact vs fuzzy), or failure mode for an unknown suburb is described.

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 description names the exact artifact ('Development Applications card in the Development section') and enumerates the payload: a count plus a list with address, type and status. That is a specific verb-plus-resource statement. It does not, however, distinguish this bundle from the near-identically named siblings such as suburbs_development_applications, suburbs_development_da_count and suburbs_development_da_list, which an agent would need in order to choose correctly.

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?

Usage is only implied by the phrase 'Shown in the suburb report as the Development Applications card', which tells the agent where the data surfaces in a UI but not when to call this tool instead of the sibling da_count or da_list tools. No exclusions, prerequisites, or alternative routing are given.

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?