Skip to main content
Glama

Heart Homes — Dubai property data

Monthly price history

get_price_history
Read-only

Monthly transaction counts and median prices for a community/area slug (or city-wide when slug is omitted), for sales or rents, optionally filtered to one property class. Rent medians are annual contract values in AED/year.

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": {
      "kind": "<kind>"
    },
    "name": "get_price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes'sale' = DLD sales transactions, 'rent' = Ejari rent contracts
slugNoOmit for city-wide history
monthsNo
propertyClassNoProperty class filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely non-obvious semantics: rent medians are annual contract values in AED/year, which an agent could easily misreport. It does not address result ordering or volume of returned months, a minor gap.

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, both load-bearing: the first defines scope and output, the second resolves the most likely unit misinterpretation. No filler or restatement of the title.

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 no output schema, the description correctly names the returned metrics (counts and medians) and their cadence (monthly). Complete enough to call correctly; only result ordering and handling of sparse months are unstated, which is a modest omission for an analytics query.

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

Parameters4/5

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

Schema coverage is 75%, and the description still adds value beyond it: it explains that omitting slug yields city-wide history and pins down the unit convention for rent medians. The 'months' window is left to the schema's default/min/max, which is adequate.

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 resource and output ('monthly transaction counts and median prices') with explicit scope rules (community/area slug or city-wide when omitted), a sale/rent dimension, and an optional property-class filter. This clearly separates it from point-in-time siblings like check_asking_price or get_location_stats.

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 historical/time-series framing implies when to use it versus snapshot tools, and the city-wide fallback behavior is stated. However, no sibling tool is named and there is no explicit 'use X instead when...' guidance for the many overlapping analytics tools.

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