NSW Planning Data (x402)

Get counts of NSW complying development certificates (CDCs) by status, application type and council.

nsw_cdc_get_summary

Read-onlyIdempotent

Get counts of NSW complying development certificates (CDCs) by status, application type and council. Call it before nsw_cdc_search_applications or nsw_cdc_search_nearby_applications: it returns the total loaded and by_status, by_application_type and by_council lists of { key, count }, whose keys are the exact filter values those tools accept. Filters are optional and combine with AND; without them the counts cover all of NSW. Counts refresh every 6 hours while the history backfill extends coverage back to 2021. Free, no payment needed. 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_get_summary"
  }
}

Input Schema

Name	Required	Description
`status`	No	Application status, exact and case-sensitive; valid values are the keys of by_status in nsw_cdc_get_summary (e.g. Approved)
`council`	No	Council name or part of it, case-insensitive; matches every council whose name contains it. Full names are in by_council of nsw_cdc_get_summary (e.g. Parramatta)
`application_type`	No	Application type, exact and case-sensitive; valid values are the keys of by_application_type in nsw_cdc_get_summary (e.g. Complying Development Certificate Application)

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.

Changed3 schema fields changedOct 29, 2026

changedInput schema / properties / application_type / description

Previous value: -"Application type, exact match (e.g. Complying Development Certificate Application)"New value: +"Application type, exact and case-sensitive; valid values are the keys of by_application_type in nsw_cdc_get_summary (e.g. Complying Development Certificate Application)"

changedInput schema / properties / council / description

Previous value: -"Council name, partial case-insensitive match (see by_council in /summary) (e.g. Parramatta)"New value: +"Council name or part of it, case-insensitive; matches every council whose name contains it. Full names are in by_council of nsw_cdc_get_summary (e.g. Parramatta)"

changedInput schema / properties / status / description

Previous value: -"Application status, exact match (e.g. Approved)"New value: +"Application status, exact and case-sensitive; valid values are the keys of by_status in nsw_cdc_get_summary (e.g. Approved)"

AddedOct 5, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare this as a read-only, idempotent, non-destructive, closed-world operation. The description adds substantial behavioral context beyond annotations: return shape, filter behavior, refresh cadence, historical backfill coverage to 2021, cost, and data source/licensing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and sibling-routing guidance, then adds only operationally relevant details. Every sentence contributes useful context without unnecessary repetition.

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?

An output schema exists, but the description still usefully previews the returned aggregate structure and keys. With rich annotations and complete schema coverage, the definition gives the agent enough context to select and invoke the tool 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 description coverage is 100%, so the schema already documents each filter parameter in detail. The description still adds useful semantics by explaining that filters are optional, combine with AND, and that omitting them produces all-NSW counts, plus how summary keys map to sibling filter values.

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 states a specific verb and resource: get counts of NSW complying development certificates. It also names the exact aggregation dimensions (status, application type, council), which makes the tool distinguishable from the sibling application-search tools.

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?

It explicitly instructs the agent to call this before nsw_cdc_search_applications or nsw_cdc_search_nearby_applications and explains why: the returned keys are the exact filter values those tools accept. It also clarifies that filters are optional and combine with AND, with no filters covering all of NSW.

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?