NSW Planning Data (x402)

Get the planning controls, lot and development applications for a NSW address in one call.

nsw_property_get_planning_report

Read-onlyIdempotent

Get the planning controls, lot and development applications for a NSW address in one call. Pass address (e.g. '5A Atkins Rd, Ermington') or lat and lng. Returns the lot and plan, zoning, maximum building height, floor space ratio, minimum lot size, heritage listings and special planning areas, each linked to its planning instrument, plus development applications and CDCs on the site and within radius_m (default 200, max 500), 10 of each, nearest first. Council DCP controls such as setbacks are not included. An unknown or ambiguous address returns an error with suggestions and is not charged. Costs $0.05 per call, paid via x402 in USDC on Base; the first 3 paid-tool calls per day are free for MCP clients while a shared daily allowance lasts. Without x402 support, later calls return the payment requirements as an error result. Failed calls are not charged. Source: NSW Department of Planning, Housing and Infrastructure; NSW Spatial Services, CC BY 3.0 AU and CC BY 4.0.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nsw_property_get_planning_report"
  }
}

Input Schema

Name	Required	Description
`lat`	No	Latitude, instead of address
`lng`	No	Longitude, instead of address
`address`	No	NSW street address with suburb (e.g. 5A Atkins Rd, Ermington)
`radius_m`	No	Radius for nearby applications in metres (default 200, max 500)

Output 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.

AddedOct 25, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it discloses $0.05 per call via x402 in USDC on Base, the 3-free-calls daily allowance, that failed or unresolved-address calls are not charged, and that clients without x402 support receive payment requirements as an error result. It also caps radius_m at 500 and results at 10 per category, nearest first. Nothing contradicts the readOnlyHint=true, destructiveHint=false annotations.

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 inputs, then return contents, then exclusions and payment mechanics. Dense but every clause carries information; the licensing/source footer is the only part that could be trimmed for an agent deciding whether to call.

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?

For a paid, zero-required-parameter aggregation tool with an output schema, the description covers inputs, returned fields, result caps, exclusions, error behavior, and billing. An agent has everything needed to decide and invoke 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 the baseline is 3, and the description earns above that by restating the address example, the lat/lng alternative, and the radius default (200) and maximum (500) in operational context rather than only schema prose.

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 ('Get') and resource set ('planning controls, lot and development applications for a NSW address') with the distinguishing scope 'in one call'. That aggregation framing separates it cleanly from the single-purpose siblings nsw_da_get_application and nsw_cdc_get_application.

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

Usage Guidelines4/5

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

Gives a clear entry condition — pass address or lat/lng — and sets the boundary by naming what is out of scope ('Council DCP controls such as setbacks are not included'). It also explains the failure path (unknown/ambiguous address returns an error with suggestions). It stops short of explicitly naming sibling alternatives for narrower lookups, but the 'one call' framing implies the aggregation trade-off.

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

All NSW Planning Data (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?