Skip to main content
Glama

Heart Homes — Dubai property data

Ready vs off-plan (secondary market) split

get_ready_vs_offplan
Read-only

Sales split between the secondary (ready / resale) market and the off-plan (pre-completion developer) market for one community or area over the last 12 months - transaction count, total value, and median price for each. "ready" = completed homes resold on the secondary market; "off-plan" = pre-completion developer sales. Property flipping, reselling, and "resale market" questions are READY / secondary-market questions: report the ready row here and do not present off-plan figures as flipping or resale figures. Optionally filter to one property class.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_ready_vs_offplan"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesLocation slug (community or area) as returned by search_locations
propertyClassNoProperty class filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real value by disclosing the fixed 12-month window, the aggregation level (one community or area), and the three returned metrics. It doesn't mention data freshness/lag or whether the two segments always sum to the total, which would have pushed it to a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The core purpose and metrics are front-loaded, and the segment definitions plus the flipping/resale disambiguation directly prevent a common misreading. Slightly repetitive — the ready/off-plan contrast is stated twice — but every sentence carries useful signal.

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 only two params, full schema coverage, and no output schema, the description does the necessary work: it names the time window, the grain of aggregation, and the exact fields returned. Only the lack of data-freshness and total-vs-segment-consistency detail keeps it below complete.

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% — the slug param already documents itself as a location slug from search_locations, and the propertyClass enum is self-explanatory. The description only adds that the property-class filter is optional, which is marginal, so the baseline 3 applies.

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+resource (sales split between secondary and off-plan markets for one community/area) and enumerates the metrics returned: transaction count, total value, median price. It also defines both segments explicitly, so no sibling tool could be confused for it.

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 routing rule: flipping, reselling, and 'resale market' questions are READY/secondary-market questions and should report the ready row only, with off-plan figures explicitly excluded from those labels. It does not point to a named alternative tool (e.g. list_recent_transactions or get_location_stats) for the off-plan or transaction-level cases, so the routing is informative but not exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources