Skip to main content
Glama

NSW Development Applications (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; clients without x402 support receive 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.

Input Schema

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

Output Schema

TableJSON 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.7/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description layers on genuinely non-derivable behavior: cost of $0.005 per call, x402/USDC-on-Base payment mechanics, the error result for clients lacking x402 support, no charge on failed or unknown-PAN calls, and the not_found return for unknown numbers. This is exactly the kind of context structured fields 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.

Conciseness5/5

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

Front-loads purpose, then sourcing, then payment/failure semantics, then attribution — a sensible ordering with no filler. The long field enumeration is the only candidate for trimming, but it is bounded and directly supports the 'full record' claim.

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-value detail is technically optional; the description still supplies it plus payment, failure, and provenance behavior. For a single-parameter tool, nothing an agent needs to invoke it correctly — input source, cost, and error semantics — 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% and the single 'pan' property is self-documented with a format example (PAN-624302). The description adds provenance meaning beyond the schema by stating where valid PAN values originate (the search tools), which helps the agent construct a correct call rather than merely format it.

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 the full record of one of the NSW development applications') scoped by a named identifier (PAN). It explicitly distinguishes itself from the search siblings by naming them as the source of PANs and by describing the breadth of the returned record, so an agent can separate it from nsw_da_get_summary and nsw_da_search_applications without opening schemas.

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 a clear prerequisite chain: 'Take PAN numbers from search_applications or search_nearby_applications,' which tells the agent where valid input comes from. It does not explicitly state when to prefer this over nsw_da_get_summary or what to do if a PAN is not yet known beyond searching, so it stops short of full when/when-not guidance.

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

All NSW Development Applications (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