NSW Planning Data (x402)

Get the full record of one of the NSW complying development certificates (CDCs) by its Planning Portal CDC number.

nsw_cdc_get_application

Read-onlyIdempotent

Get the full record of one of the NSW complying development certificates (CDCs) by its Planning Portal CDC number. Returns every location with lot and plan, all development types, submission, lodgement, determination and exhibition dates, cost, dwellings, storeys, lots and the remaining source fields. Take CDC numbers from search_applications or search_nearby_applications. An unknown number returns not_found and is not charged. Costs $0.005 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

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cdc": "<cdc>"
    },
    "name": "nsw_cdc_get_application"
  }
}

Input Schema

Name	Required	Description	Default
`cdc`	Yes	Planning Portal CDC number (e.g. CDC-388198)

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.6/5.0

Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, but the description adds substantial paid-tool context: per-call cost, free daily allowance, x402/USDC payment mechanics, behavior when x402 is unsupported, and that unknown or failed calls are not charged. This is rich behavioral disclosure beyond structured 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?

The description is front-loaded with the core action and identifier source before moving into return fields, pricing, and licensing. It is somewhat long, but almost every sentence carries operational value for an agent invoking a paid tool.

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?

The tool has an output schema, so return values need not be detailed, yet the description still summarizes them helpfully. For a paid, single-parameter read tool with rich annotations, the definition covers sourcing, pricing, failure behavior, and licensing sufficiently for correct invocation.

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?

The single parameter is fully covered by the schema (100% coverage), including an example value. The description adds useful semantic context by explaining that the CDC number should come from the sibling search tools, which goes slightly beyond the schema's basic type and example.

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?

The description uses a specific verb and resource: 'Get the full record of one of the NSW complying development certificates (CDCs)' by Planning Portal CDC number. It clearly distinguishes this full-record tool from the sibling search tools and summary tools by emphasizing 'full record' and naming the identifier.

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?

It explicitly tells the agent where to obtain CDC numbers: 'Take CDC numbers from search_applications or search_nearby_applications.' It does not explicitly compare against nsw_cdc_get_summary, so there is a small gap, but the usage context is clear and actionable.

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?