NSW Planning Data (x402)

Find NSW complying development certificates (CDCs) within 2 km of a street address or latitude/longitude, nearest first.

nsw_cdc_search_nearby_applications

Read-onlyIdempotent

Find NSW complying development certificates (CDCs) within 2 km of a street address or latitude/longitude, nearest first. Pass address (e.g. '10 Brigalow Ave, Casula') and it is geocoded against the official NSW address register, or pass lat and lng. Returns the distance in metres for each result plus the same fields as search_applications; meta.geocode shows the matched address. An unknown or ambiguous address returns an error with suggestions and is not charged. lodged_from limits results to recent applications. Costs $0.02 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 Planning Portal), 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_cdc_search_nearby_applications"
  }
}

Input Schema

Name	Required	Description
`lat`	No	Latitude (WGS84); required unless address is given (e.g. -33.81)
`lng`	No	Longitude (WGS84); required unless address is given (e.g. 151.06)
`limit`	No	Max results, 1-100 (default 20)
`address`	No	NSW street address with suburb; alternative to lat/lng (e.g. 10 Brigalow Ave, Casula NSW 2170)
`radius_m`	No	Radius in metres, 1-2000 (default 500)
`lodged_from`	No	Lodgement date lower bound, yyyy-mm-dd

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 5, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well past the read-only/idempotent annotations: discloses the geocoding dependency, that ambiguous addresses return an error with suggestions and are not charged, the $0.02 x402/USDC-on-Base cost with a 3-call free tier, and that unsupported clients get payment requirements back as an error. This is exactly the operational context annotations cannot carry.

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 the core purpose and input modes before the payment mechanics, and every sentence carries usable information. The x402/free-tier/source-attribution block is long but genuinely needed for a paid tool, so it is padding only at the margins.

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?

With an output schema present, the description need not enumerate return fields; it still flags distance-in-metres and meta.geocode for the matched address, and covers failure modes and billing behaviour. For a paid, geocoding-backed read tool, nothing an agent needs before calling is missing.

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

Parameters3/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. The description restates the address-vs-lat/lng alternative and mentions lodged_from's effect, but adds little beyond the schema and does not reconcile the 'within 2 km' framing with the actual radius_m default of 500 m, which could mislead an agent about the effective search radius.

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 (find NSW CDCs), a precise scope (within 2 km, nearest first), and immediately frames the two input modes. It is clearly distinguishable from the sibling nsw_cdc_search_applications, which is invoked by name as the field-equivalent non-geo search.

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 clear situational context: supply an address (geocoded against the official NSW register) or supply lat/lng, and use lodged_from to restrict to recent applications. It does not explicitly say when to prefer this over nsw_cdc_search_applications or nsw_da_search_nearby_applications, so the routing is only implied.

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?