io.github.resuly/daleads-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DALEADS_API_KEY | No | API key for the DA Leads API. Required for paid tools, but property sample tools work without it. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_dasA | Search development applications with filters. Args: state: Filter by state (NSW, VIC, QLD, SA, WA, TAS, NT, ACT) council: Filter by council name (e.g. "City of Melbourne") category: Filter by trade category (e.g. "Renovation / Extension", "Swimming Pool / Spa") suburb: Filter by suburb name postcode: Filter by exact postcode since: Only show DAs lodged on or after this ISO date (YYYY-MM-DD) status_group: Normalized status: pending, advertised, approved, rejected, or other is_residential: Filter residential (true) or commercial (false) page: Page number (default 1) limit: Results per page (max 100) |
| get_daA | Get full details of a specific development application by ID. Args: da_id: The DA record ID |
| nearby_dasA | Find development applications near a location. Args: lat: Latitude lng: Longitude radius_km: Search radius in km (default 5, max 50) category: Filter by trade category since: Only show DAs lodged on or after this ISO date (YYYY-MM-DD) status_group: Normalized status: pending, advertised, approved, rejected, or other page: Page number (default 1) limit: Results per page (max 100) |
| list_categoriesA | List all trade categories with record counts. Returns categories like: Renovation / Extension, Swimming Pool / Spa, Granny Flat / Secondary Dwelling, Demolition, etc. |
| list_councilsA | List councils with state, DA count, and last activity date. Args: limit: Max councils to return |
| get_statsA | Get overall DA statistics: total records, by state, by category, date range. |
| sql_queryA | Run a read-only SQL query against DA records. Pro plan only. Query the 'das' table with columns: id, address, address_suburb, address_postcode, council_name, council_reference, state, trade_category, sub_category, application_type, is_residential, lodgement_date, status, cost_of_development, decision_date, decision_status, on_notice_from, on_notice_to, number_of_dwellings, lot_count, land_use, building_type, storeys, latitude, longitude, data_source, date_fetched, documents, info_url. Description and summary are deliberately unavailable because council free text may contain personal contact details. Max 1000 rows. 10 second timeout. SELECT only. Args: query: SQL SELECT query using table name 'das' params: Optional parameters for %s placeholders |
| property_intelligenceA | Full property intelligence profile for one Australian address (or lat/lng point). Returns planning (zones, overlays, heritage), hazards (flood, bushfire), environment, transport, nearby DAs, points of interest and scored risk components for the address. Requires an API key on a Property Intelligence plan; each lookup counts toward the key's monthly quota, except the sandbox addresses from property_sandbox_addresses which are never metered. No key? Use property_sample for a complete keyless example first. Args: address: Free-text address, e.g. "34 Mary St Clayton VIC" lat: Latitude (alternative to address) lng: Longitude (alternative to address) components: Optional comma-separated subset to return, e.g. "scores.noise,hazards,das". Blocks: das, poi, planning, hazards, environment, transport, utilities, administrative, public_housing, scores. |
| property_sampleA | Complete real Property Intelligence response, no API key required. Returns the canned production payload for 163 Grattan St, Carlton VIC (heritage terrace with DA activity) so you can inspect the full response shape before requesting a key. |
| property_flood_sampleA | Real flood score component example, no API key required. Returns the production scores.flood block for a study-covered Rocklea QLD point: official 1% AEP modelled depth, overlay status, terrain context and provenance. |
| property_sandbox_addressesA | List sandbox addresses whose lookups never count toward your quota. Twelve real addresses covering all eight states; use them with property_intelligence to evaluate live responses for free on any Property Intelligence key. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools have clear, distinct purposes. search_das and nearby_das both find DAs but by different criteria (filters vs. location), and property_intelligence is broader than nearby_das. The sample tools are clearly demos. Minor potential confusion between search_das and nearby_das when both are applicable, but descriptions mitigate.
Naming is mixed: verb_noun (search_das, get_da, list_categories, list_councils, get_stats), descriptive (nearby_das, sql_query), and a property_* prefix group (property_intelligence, property_sample, property_flood_sample, property_sandbox_addresses). No consistent verb or noun pattern across the entire tool set.
11 tools is well-scoped for a DA lookup and property intelligence server. Each tool contributes a distinct capability: search, get, nearby, metadata, stats, SQL access, and property intelligence samples. No redundant or excessive tools.
The tool surface covers the domain comprehensively: searching with many filters, retrieving full details, geospatial search, metadata lists, statistics, and raw query capability. Property intelligence adds a complementary feature set. No obvious gaps such as missing update/create, which are irrelevant for a read-only public data API.