Skip to main content
Glama

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Suburb · DA count + DA list — bundle

suburbs_development_all
Read-onlyIdempotent

DA count + DA list — bundle

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
suburb_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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": [
-        {
-          "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
  2. First observed

TDQS

D1.9/5.0
Behavior2/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 safety profile is covered. However, the description adds no behavioral context: it does not mention what data is returned, whether it is a combined response or two separate results, or any pagination/format details. The bar is lower because of annotations, but the description still fails to add any beyond them.

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 extremely short (four words) but this is under-specification, not concise efficiency. Like the 'Process' example, it carries no substantive information and cannot adequately describe the tool's purpose or behavior. The sentence structure is technically clean but fails to communicate meaning.

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

Completeness2/5

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

With no output schema and minimal description, the tool is incomplete. The agent cannot know what 'DA' means (presumably development applications), what the response looks like, or why this bundle differs from calling the individual count/list tools. The sibling tool names provide some context, but the description itself leaves critical gaps.

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 provides no explanation of the 'suburb_name' parameter. Although the parameter's name is self-explanatory, the description must compensate for the missing schema documentation and does not. The agent gets no help understanding required formats, expectations, or the relationship of this parameter to the bundled data.

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?

Description is essentially a restatement of the title: 'DA count + DA list — bundle' adds no verb or explicit resource beyond the title's 'Suburb · DA count + DA list — bundle'. It is a tautology that relies entirely on the name and title for meaning, so an agent cannot determine what the tool actually does without external context.

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 guidance is provided on when to use this tool versus alternatives. The sibling list includes suburbs_development_da_count and suburbs_development_da_list, and the 'bundle' in the name implies combining both, but the description never states that this tool is for retrieving both together or when that is preferable.

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