Skip to main content
Glama

Get what is being built near a NSW address: development applications and CDCs, summarised.

nsw_property_get_development_activity
Read-onlyIdempotent

Get what is being built near a NSW address: development applications and CDCs, summarised. Answers questions such as "what is being built near this address" in one call. Pass address or lat and lng. Merges development applications and complying development certificates lodged within radius_m (default 500, max 2000) in the last months (default 24, max 120) and returns totals (applications, new dwellings, total cost), counts by status, development type and year, the 5 largest by cost, and the newest limit applications (default 20, max 50) with distance, status, cost and dates. Use nsw_property_get_planning_report for the zoning and controls of the site itself, and nsw_da_get_application or nsw_cdc_get_application for one record in full. capped is true when more than 2000 records of one kind matched; the summary then covers the nearest ones. An unknown or ambiguous address returns an error with suggestions and is not charged. Costs $0.03 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_development_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoLatitude in decimal degrees, instead of address
lngNoLongitude in decimal degrees, instead of address
limitNoNewest applications to list, 1-50 (default 20); totals cover all matches
monthsNoLodgement window in months back from today, 1-120 (default 24)
addressNoStreet number, street and suburb; or pass lat and lng (e.g. 5A Atkins Rd, Ermington)
radius_mNoSearch radius in metres, 1-2000 (default 500)

Output Schema

NameRequiredDescriptionDefault
dataNoResult: a list of applications for search and nearby tools, one record or summary object otherwise
metaYesPaging and query details, e.g. limit, offset, has_more, count
attributionYesSource attribution; keep it when presenting the data

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description's added value is cost and failure behavior: $0.03 per call via x402, three free calls per day, failed calls uncharged, and unknown/ambiguous addresses returning suggestions rather than a charge. Also discloses the 'capped' truncation semantics at >2000 records. Slight gap: the 'shared daily allowance' clause is vague about what an agent should do when exhausted.

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-loaded with the verb and the question it answers, then parameters, then alternatives, then cost — a sensible order. It is dense and the payment/licensing tail is long, but nearly every sentence carries operational information; only the license attribution is arguably non-essential for selection.

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?

Despite an output schema existing, the description usefully enumerates the returned aggregates (totals, counts by status/type/year, top 5 by cost, newest N with distance), which is what lets an agent know one call suffices. Combined with cost, error, and truncation behavior, nothing needed for correct invocation is missing.

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; the description goes further by stating ranges and defaults inline (radius 500/2000, months 24/120, limit 20/50) and by clarifying the key semantic that totals cover all matches while only `limit` records are listed. It also explains the address-vs-lat/lng choice in prose rather than leaving it to the schema.

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 — 'get what is being built near a NSW address: development applications and CDCs, summarised' — and explicitly contrasts itself with three sibling tools (nsw_property_get_planning_report, nsw_da_get_application, nsw_cdc_get_application). An agent can place this tool in the family without opening a schema.

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 concrete when-to-use framing ('answers questions such as "what is being built near this address" in one call') plus explicit routing: use the planning report for site zoning/controls, the get_* tools for a single record in full. Both alternatives and the condition selecting them are named.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources