NSW Development Applications (x402)

Search NSW development applications by council, suburb, postcode or lodgement date, newest lodgement first.

nsw_da_search_applications

Read-onlyIdempotent

Search NSW development applications by council, suburb, postcode or lodgement date, newest lodgement first. Returns up to 100 development applications per call with address, status, cost, dwellings, storeys and development types, plus has_more for paging with offset. status, application_type, development_type and min_cost must be combined with council, suburb or postcode. Use get_application for the full record of a result. Costs $0.01 per call, paid via x402 in USDC on Base; clients without x402 support receive the payment requirements as an error result. Failed calls are not charged. Source: NSW Department of Planning, Housing and Infrastructure (NSW Planning Portal), CC BY 4.0.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Page size, 1-100 (default 20)
`offset`	No	Number of results to skip, 0-1000 (default 0)
`status`	No	Application status, exact match (e.g. Determined)
`suburb`	No	Suburb of the primary address, case-insensitive (e.g. ERMINGTON)
`council`	No	Council name, partial case-insensitive match (see by_council in /summary) (e.g. Parramatta)
`min_cost`	No	Minimum estimated cost of development in AUD (e.g. 1000000)
`postcode`	No	4-digit postcode of the primary address (e.g. 2115)
`lodged_to`	No	Lodgement date upper bound, yyyy-mm-dd (e.g. 2026-06-30)
`lodged_from`	No	Lodgement date lower bound, yyyy-mm-dd (e.g. 2026-01-01)
`application_type`	No	Application type, exact match (e.g. Development Application)
`development_type`	No	Development type, partial match (e.g. dwelling)

Output Schema

TableJSON Schema

Name	Required	Description
`data`	No	Result: a list of applications for search and nearby tools, one record or summary object otherwise
`meta`	Yes	Paging and query details, e.g. limit, offset, has_more, count
`attribution`	Yes	Source attribution; keep it when presenting the data

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "attribution": {
+      "additionalProperties": false,
+      "description": "Source attribution; keep it when presenting the data",
+      "properties": {
+        "licence": {
+          "type": "string"
+        },
+        "licenceUrl": {
+          "type": "string"
+        },
+        "publisher": {
+          "type": "string"
+        },
+        "text": {
+          "description": "Attribution text to show alongside the data",
+          "type": "string"
+        }
+      },
+      "required": [
+        "publisher",
+        "licence",
+        "licenceUrl",
+        "text"
+      ],
+      "type": "object"
+    },
+    "data": {
+      "description": "Result: a list of applications for search and nearby tools, one record or summary object otherwise"
+    },
+    "meta": {
+      "additionalProperties": {},
+      "description": "Paging and query details, e.g. limit, offset, has_more, count",
+      "type": "object"
+    }
+  },
+  "required": [
+    "meta",
+    "attribution"
+  ],
+  "type": "object"
+}

First observedOct 4, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the readOnly/idempotent/non-destructive annotations by disclosing the 100-result cap, has_more paging, the $0.01 x402 USDC-on-Base payment requirement, the error-result behavior for clients lacking x402, and that failed calls are not charged. These are material operational facts an agent cannot infer from structured fields.

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?

Front-loads purpose, then returns, then the filter constraint, then cost/payment, then provenance. Dense and information-bearing throughout, though the single block of prose runs long and could be broken into clearer segments.

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

Completeness5/5

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

Covers purpose, filtering constraints, result shape, pagination, pricing and error behavior, plus source/licence attribution. Even though an output schema exists, the extra payment and combination rules leave nothing an agent needs to call this correctly.

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 100%, so per-parameter formats are already documented and the baseline would be 3. The description adds genuine cross-parameter semantics, though: the dependency that status/application_type/development_type/min_cost are only valid when combined with a location filter, which the schema cannot express.

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

Purpose5/5

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

States a specific verb and resource ('Search NSW development applications') with the filter axes (council, suburb, postcode, lodgement date) and the sort order. It also distinguishes itself from nsw_da_get_application by naming that sibling as the way to fetch a full record.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit usage rule: 'status, application_type, development_type and min_cost must be combined with council, suburb or postcode.' It also routes the agent to get_application for full records, so both the constraint and the alternative are spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All NSW Development Applications (x402) 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?