Skip to main content
Glama

Heart Homes — Dubai property data

Location statistics

get_location_stats
Read-only

Headline stats for one community or area slug: 12-month sales volume, median price, price per sqm, 12-month trend, plus a property-class mix for sales and rents. When propertyClass is set for a community, also returns per-bedroom sales and rent breakdowns; rent bedroom coverage is partial and must be reported as approximate using rentBedroomCoveragePct and rentBedroomNote. Per-bedroom rent for a single building is not available.

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_location_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesLocation slug (community or area) as returned by search_locations
propertyClassNoWhen set, also return the per-bedroom sales breakdown and, where attributable, a per-bedroom rent breakdown with partial-coverage figure (communities only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only state the read-only, non-destructive profile; the description adds substantive behavioral disclosure beyond that. It warns that rent bedroom coverage is partial, prescribes that results must be reported as approximate, and names the exact fields (rentBedroomCoveragePct, rentBedroomNote) an agent must surface — a real data-quality contract, not a restatement.

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?

Three sentences, all earning their place: sentence one front-loads the returned metrics, sentence two covers the propertyClass conditional path, sentence three gives the negative boundary. Dense but zero filler, and the primary purpose is first.

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 carries the return-value burden and does so well by naming each returned metric and its companion coverage fields. It stops just short of describing the shape of the property-class mix or area-slug behavior when no class is set, but nothing needed to call the tool correctly is missing.

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 coverage is 100% and the propertyClass schema text already explains the per-bedroom breakdown and 'communities only' condition. The description largely restates that behavior, adding only the reiteration of partial coverage; it contributes little syntax or format detail beyond the schema, so 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 ('headline stats for a location') and enumerates exactly what comes back: 12-month sales volume, median price, price per sqm, trend, and property-class mix. The 'plus bedroom breakdowns' and 'no rent breakdown at building level' framing lets an agent distinguish this from get_building_stats and get_market_extended without opening a schema.

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?

Usage is implied by the 'one community or area slug' scope and the exclusion 'per-bedroom rent for a single building is not available', which steers building queries elsewhere. However, no sibling is named explicitly (get_building_stats, get_market_overview, rank_communities), so an agent must infer the routing from the sibling list rather than the description.

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