Skip to main content
Glama
Sign In

NSW Planning Data (x402)

by io.github.zuo305
OverviewDiscussionsAdmin

Get the full record of one of the NSW development applications by its Planning Portal application number (PAN).

nsw_da_get_application
Read-onlyIdempotent

Get the full record of one of the NSW development applications by its Planning Portal application number (PAN). 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 PAN 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": {
      "pan": "<pan>"
    },
    "name": "nsw_da_get_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
panYesPlanning Portal application number (PAN) (e.g. PAN-624302)

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. Changed1 schema field changed
    • changedInput schema / properties / pan / description
      Previous value: -"Planning Portal application number (e.g. PAN-624302)"New value: +"Planning Portal application number (PAN) (e.g. PAN-624302)"
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "attribution": {
+      "additionalProperties": false,
+      "description": "Source attribution; keep it when presenting the data",
+      "properties": {
+        "licence": {
+          "type": "string"
+        },
+        "licenceUrl": {
+          "type": "string"
+        },
+        "publisher": {
+          "type": "string"
+        },
+        "text": {
+          "description": "Attribution text to show alongside the data",
+          "type": "string"
+        }
+      },
+      "required": [
+        "publisher",
+        "licence",
+        "licenceUrl",
+        "text"
+      ],
+      "type": "object"
+    },
+    "data": {
+      "description": "Result: a list of applications for search and nearby tools, one record or summary object otherwise"
+    },
+    "meta": {
+      "additionalProperties": {},
+      "description": "Paging and query details, e.g. limit, offset, has_more, count",
+      "type": "object"
+    }
+  },
+  "required": [
+    "meta",
+    "attribution"
+  ],
+  "type": "object"
+}
  3. First observed

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, and closed-world behavior. The description adds substantial operational context beyond annotations: unknown numbers return not_found and are not charged, failed calls are not charged, pricing is $0.005 per call via x402 in USDC on Base, the first 3 paid-tool calls per day are free, and unsupported clients receive payment requirements as an error.

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 purpose and return fields, then moves into operational and payment details. It is somewhat long, but every sentence carries useful information for invocation, error handling, or billing.

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, so return values need not be exhaustively specified, though the description still outlines the returned record. It covers the key error case, billing behavior, payment mechanics, and data source, leaving no important operational gap for an agent invoking this paid lookup tool.

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 schema already defines the single pan parameter with an example. The description adds workflow meaning by stating that PAN numbers should be taken from the search tools, which helps the agent supply a valid identifier rather than guessing.

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 an NSW development application by PAN. It clearly distinguishes this detail lookup from the search siblings by stating it returns the complete set of fields, and it is obviously different from the summary tool by emphasizing 'full record.'

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 PAN values should come from: search_applications or search_nearby_applications. It also states the not_found behavior for unknown PANs. It does not explicitly contrast with nsw_da_get_summary, but the usage context is otherwise clear.

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) toolsInspect
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