MRK Dubai Property

Search Dubai projects

search_projects

Read-onlyIdempotent

Search ~2,400 Dubai residential projects (DLD-registered plus MRK-researched new launches). Filter by community, developer, stage, handover year, starting-price range, bedrooms and type. Returns compact summaries with canonical URLs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_projects"
  }
}

Input Schema

Name	Required	Description	Default
`sort`	No	Sort order	relevance
`type`	No	Property type
`limit`	No	Max results (1-50)
`query`	No	Free text matched against name, developer, community and summary
`status`	No	Construction stage
`bedrooms`	No	Bedroom count offered (0 = studio)
`community`	No	Community name or slug, e.g. 'Dubai Hills Estate' or 'business-bay'
`developer`	No	Developer name or slug, e.g. 'Emaar' or 'sobha-realty'
`maxPriceAed`	No	Maximum developer starting price in AED
`minPriceAed`	No	Minimum developer starting price in AED (projects without a price are excluded when set)
`handoverYear`	No	Handover / completion year, e.g. 2027

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered. The description adds genuinely new context: the size and provenance of the corpus and the fact that results are compact summaries with canonical URLs, which tells the agent what it will get back and that a follow-up get_project call may be needed for detail.

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?

Two sentences, zero filler, with the corpus scope front-loaded before the filter list and the return shape. Nothing is repeated or wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 11 fully documented optional parameters and no output schema, the description supplies the missing return-value context ('compact summaries with canonical URLs') and the dataset scope. It could go further by noting pagination or result-count behavior, but it is sufficient to call the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every parameter is already documented, including the minPriceAed exclusion rule and the studio=0 convention. The description only restates the filter categories at a high level, adding no syntax or format detail beyond the schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search ~2,400 Dubai residential projects') and scopes the corpus (DLD-registered plus MRK-researched new launches). It does not explicitly name a sibling to contrast with, so an agent must infer that this is the project-level search rather than search_listings or compare_projects.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description enumerates the filterable dimensions, which implies when the tool is useful, but it never states when to prefer it over search_listings, compare_projects, or get_project. No exclusions or prerequisites are given.

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

All MRK Dubai Property tools Inspect

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

Need Help?