suburbs_development_allWhat 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.
| 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": [
- {
- "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: +nullDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description usefully discloses what the result contains (count plus per-application address/type/status), which matters because there is no output schema, but it omits any pagination, result-size, or freshness behavior for the list portion.
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?
Two sentences, with the concrete 'what it returns' content front-loaded. The second interpretive sentence earns some place by framing how to read the data, though it edges toward flourish.
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 single-parameter read-only tool with no output schema, the description explains the returned contents adequately, but it leaves unanswered the suburb_name format and the potential size/pagination of the DA list. It is workable but not fully complete.
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?
The single parameter (suburb_name) has 0% schema description coverage, so the description carries the burden but adds no meaning about its format, e.g. whether a postcode, state, or exact suburb string is expected. It never references the parameter at all.
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 states a specific verb and resource: it returns the count of development applications and the list itself, naming the fields (address, type, status). The title signals it is a 'bundle' of the count and list, but the description never names the sibling tools (suburbs_development_da_count, suburbs_development_da_list) it aggregates, so differentiation is implicit rather than explicit.
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?
There is no when-to-use guidance and no routing to alternatives. The second sentence ('Read it as supply coming down the pipeline...') is analytical framing for interpreting the result, not guidance on when to pick this tool over suburbs_development_da_count or suburbs_development_da_list.
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.