Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Suburb · Development Applications

suburbs_development_applications
Read-onlyIdempotent

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

Development applications in the suburb, newest first, with category counts.

Paginated with limit/offset: total_available is every application we hold for the suburb, total is how many this page returned, and next_offset is the next page's offset (null on the last). min_date / max_date span the full history. Each page is one call at a flat price.

Price: 15¢ 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_applications"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoApplications to return (default 100, max 500).
offsetNoApplication offset — page with `limit`. `next_offset` in the response is the value for the next page (null on the last).
suburb_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 100,
+  "description": "Applications to return (default 100, max 500).",
+  "maximum": 500,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Application offset — page with `limit`. `next_offset` in the response is the value for the next page (null on the last).",
+  "minimum": 0,
+  "type": "integer"
+}
  2. Changed1 schema field changed
    • 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": [
-        {
-          "additionalProperties": true,
-          "description": "Recent development applications (up to 100, newest first).",
-          "example": {
-            "applications": [
-              {
-                "address": "38 Buttaba Avenue Belmont North NSW 2280",
-                "category": "New Dwelling",
-                "date": "2026-06-18",
-                "dollar_value": 271740,
-                "id": 99033512,
-                "lat": -33.02082551,
-                "lng": 151.676206648,
-                "stage": "under_assessment",
-                "stage_display": "Under Assessment",
-                "title": "Secondary dwelling"
-              }
-            ],
-            "area_level": "suburb",
-            "area_name": "Belmont North",
-            "categories": [
-              {
-                "category": "New Dwelling",
-                "count": 21
-              },
-              {
-                "category": "Renovation",
-                "count": 48
-              },
-              {
-                "category": "Demolition",
-                "count": 9
-              },
-              {
-                "category": "Other",
-                "count": 22
-              }
-            ],
-            "max_date": "2026-06-18",
-            "min_date": "2019-12-02",
-            "total": 100
-          },
-          "properties": {
-            "applications": {
-              "description": "DA records, newest first.",
-              "items": {
-                "additionalProperties": true,
-                "description": "One development application.",
-                "properties": {
-                  "address": {
-                    "anyOf": [
-                      {
-                        "type": "string"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Cleaned site address.",
-                    "title": "Address"
-                  },
-                  "category": {
-                    "description": "Coarse category from the title classifier.",
-                    "title": "Category",
-                    "type": "string"
-                  },
-                  "date": {
-                    "anyOf": [
-                      {
-                        "type": "string"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Lodged date (YYYY-MM-DD).",
-                    "title": "Date"
-                  },
-                  "dollar_value": {
-                    "anyOf": [
-                      {
-                        "type": "number"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Estimated works value (AUD).",
-                    "title": "Dollar Value"
-                  },
-                  "id": {
-                    "anyOf": [
-                      {
-                        "type": "integer"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Source DA record id.",
-                    "title": "Id"
-                  },
-                  "lat": {
-                    "anyOf": [
-                      {
-                        "type": "number"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Latitude (null for some sources, e.g. VIC).",
-                    "title": "Lat"
-                  },
-                  "lng": {
-                    "anyOf": [
-                      {
-                        "type": "number"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Longitude.",
-                    "title": "Lng"
-                  },
-                  "stage": {
-                    "anyOf": [
-                      {
-                        "type": "string"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Raw stage code (e.g. 'under_assessment').",
-                    "title": "Stage"
-                  },
-                  "stage_display": {
-                    "anyOf": [
-                      {
-                        "type": "string"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Human-readable stage.",
-                    "title": "Stage Display"
-                  },
-                  "title": {
-                    "description": "Proposed works description.",
-                    "title": "Title",
-                    "type": "string"
-                  }
-                },
-                "required": [
-                  "title",
-                  "category"
-                ],
-                "title": "DevelopmentDa",
-                "type": "object"
-              },
-              "title": "Applications",
-              "type": "array"
-            },
-            "area_level": {
-              "description": "Always 'suburb'.",
-              "title": "Area Level",
-              "type": "string"
-            },
-            "area_name": {
-              "description": "Suburb (SAL) name.",
-              "title": "Area Name",
-              "type": "string"
-            },
-            "categories": {
-              "description": "Category counts across the returned applications.",
-              "items": {
-                "description": "DA count for one category.",
-                "properties": {
-                  "category": {
-                    "description": "Education / New Dwelling / Renovation / Demolition / Commercial / Other.",
-                    "title": "Category",
-                    "type": "string"
-                  },
-                  "count": {
-                    "description": "Applications in this category.",
-                    "title": "Count",
-                    "type": "integer"
-                  }
-                },
-                "required": [
-                  "category",
-                  "count"
-                ],
-                "title": "DaCategoryCount",
-                "type": "object"
-              },
-              "title": "Categories",
-              "type": "array"
-            },
-            "max_date": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Most recent DA date on record.",
-              "title": "Max Date"
-            },
-            "min_date": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Earliest DA on record for the suburb (full history, not just the returned list).",
-              "title": "Min Date"
-            },
-            "total": {
-              "description": "Applications returned (capped at 100).",
-              "title": "Total",
-              "type": "integer"
-            }
-          },
-          "required": [
-            "area_name",
-            "area_level",
-            "total",
-            "categories",
-            "applications"
-          ],
-          "title": "SuburbDevelopmentApplications",
-          "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[SuburbDevelopmentApplications]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_SuburbDevelopmentApplications_"
-}New value: +null
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, yet the description adds genuinely non-obvious behavior: page semantics distinguishing total_available from total, the meaning of next_offset including its null sentinel on the last page, the fact that min_date/max_date span the full history rather than the page, and a flat per-call price independent of page size.

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?

Content is front-loaded: the report-card context and the core 'what you get' sentence come first, followed by pagination semantics and then price. The opening positional sentence partly duplicates the second (both restate that this returns suburb development applications), and the markdown emphasis on pricing is heavy, but overall there is little 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?

With no output schema, the description carries the burden of explaining return shape; it names several fields (total_available, total, next_offset, min_date, max_date, category counts) but does not describe the per-application record itself, so an agent still cannot anticipate what fields each application contains. For a paid, paginated tool the field inventory is the main missing piece.

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

Parameters4/5

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

Schema coverage is 67%, with limit/offset already documented in-schema (defaults, max 500, offset paging), so the baseline would be 3; the description goes further by explaining how limit/offset interact with next_offset and by making the flat-price-per-page economics explicit. It adds nothing for suburb_name, the one required parameter with no schema description, leaving its expected format unaddressed.

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?

States a specific resource and ordering ('Development applications in the suburb, newest first, with category counts') and ties itself to the 'Development Applications' card in the suburb report's Development section, so the resource is unambiguous. It does not, however, distinguish itself from very similar siblings such as suburbs_development_da_list or suburbs_development_da_count, so an agent cannot tell from this text which of the near-identical list tools to pick.

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 only implied through the placement note ('Shown in the suburb report as the ... card in the Development section'), which suggests report-card retrieval, but there is no explicit when-to-use statement, no exclusion of the DA list/count siblings, and no prerequisites. Pagination mechanics and per-call price are documented, which helps with cost-aware selection, but the alternative-selection guidance is absent.

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