dld-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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query_dldA | Query Dubai property data - sales transactions or rental contracts. Args: area: Location to search (e.g., "Marina", "JBR", "Downtown", "Palm Jumeirah", or building name) type: "sales" for DLD transactions, "rentals" for Ejari contracts property_type: "all", "apartment", "villa", or "townhouse" (sales only) bedrooms: "all", "studio", "1", "2", "3", "4", "5+" date_from: Start date YYYY-MM-DD (default: last 12 months for sales, 24 for rentals) date_to: End date YYYY-MM-DD (default: today) metric: "stats" (aggregated statistics), "count" (just count), "list" (individual records) limit: Max records for list mode (1-50, default 10) Returns: For stats: median/avg/min/max prices, transaction count, total volume For count: just the count of matching records For list: individual transaction/contract records Examples: - "How many villas sold in Palm Jumeirah in 2024?" query_dld(area="Palm", property_type="villa", date_from="2024-01-01", metric="count") |
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 1 tool
Only one tool exists, so there is no possibility of confusion between tools.
With a single tool, naming consistency is not applicable; the tool name is clear and descriptive.
A single tool for querying Dubai property data is too few for comprehensive coverage. The tool is powerful but would benefit from additional tools for different operations or data types.
The tool covers a wide range of queries with flexible parameters, but lacks operations for retrieving metadata like available areas or property types, and does not support updates or deletions.