sg-property-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
| logging | {} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_areaA | Search land use and zoning info near a Singapore address. Resolves the address to coordinates, then finds nearby land parcels with zoning details. |
| search_area_by_coordsA | Search land use and zoning info near specific coordinates. Skips geocoding — use when you already have lat/lon. |
| search_hdb_resaleA | Search HDB resale flat transactions by town and optional flat type. Data covers 2017 onwards, sorted by most recent. Returns price, floor area, storey, lease, and location details. |
| analyze_resultsA | Analyze the last search results using AI. Provides insights, patterns, and summaries. Best used after a search returns results — works with land use, HDB resale, and amenity data. |
| export_csvA | Export the last search results to a CSV file. The file must be saved within a directory approved by the client. |
| export_mdB | Export the last search results to a Markdown file. The file must be saved within a directory approved by the client. |
| search_nearby_amenitiesA | Search for nearby amenities (schools, hospitals, clinics, hawker centres, parks, MRT stations, bus stops, supermarkets, pharmacies) around a coordinate in Singapore. Returns results sorted by distance. Requires coordinates — use search_area first to geocode an address if needed. |
| get_attributionsA | Show data source attributions and licences for all data used by this server. Only call this tool when the user explicitly asks about data sources, credits, or attributions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| last-search | Returns the last search results including query parameters, results, and timestamp |
| status | Server status: name, version, uptime, search count, last search time |
TDQS
Scored across 8 tools
Tools are mostly distinct with clear purposes. Export_csv and export_md overlap but differ in format; search_area and search_area_by_coords serve same purpose with different inputs but descriptions clarify. Overall, minimal confusion.
All tool names follow a consistent verb_noun pattern in snake_case, e.g., search_area, export_csv, get_attributions. No deviations or mixed styles.
With 8 tools covering land use, HDB resale, amenities, analysis, exports, and attributions, the scope is well-focused for a property server. Not too many or too few.
Core workflows (search, export, analysis) are covered, but there are notable gaps: no direct property address lookup, no private property transaction data, and no filtering or sorting options. Agents might face dead ends.