Skip to main content
Glama

Heart Homes — Dubai property data

Rank buildings within a community

rank_buildings
Read-only

Buildings in one community ranked by 12-month median sale price or median annual rent - answers 'cheapest/most expensive buildings in X'. Rent coverage is partial: Ejari records carry no building name, so only buildings whose project name identifies them uniquely have rent stats. Buildings with fewer than 5 records are excluded.

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": {
      "communitySlug": "<communitySlug>",
      "metric": "<metric>",
      "order": "<order>"
    },
    "name": "rank_buildings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
orderYes
metricYes
communitySlugYesCommunity slug from search_locations

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/closed-world, and the description adds genuinely new behavioral context: rent stats are only available for uniquely identifiable buildings, and buildings with fewer than 5 records are excluded. That data-quality disclosure is exactly the kind of thing annotations cannot carry; only return shape/pagination behaviour is missing.

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 tight sentences: purpose first, coverage caveat second, exclusion rule third. No filler, and the most decision-relevant constraint is front-loaded.

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?

No output schema exists, so the description should be self-sufficient about results; it explains what is ranked and the coverage limits, which is enough to call correctly, but the shape of the returned per-building ranking and how limit interacts with the exclusion rule are left unstated.

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 low (25%) — only communitySlug is documented in the schema — so the description must compensate. It does cover the two metric meanings (12-month median sale price vs median annual rent) and the cheapest/most-expensive ordering, but says nothing about the limit parameter (3–15, default 10), which is the one uncovered parameter.

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+scope: buildings within one community, ranked by 12-month median sale price or median annual rent. The parenthetical example ('cheapest/most expensive buildings in X') makes it distinguishable at a glance from rank_communities and get_building_stats.

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?

The example question defines the trigger condition well and the rent-coverage caveat implicitly tells the agent when to prefer sale_price. It does not explicitly name alternatives (e.g. 'for a single building use get_building_stats', 'for the whole city use rank_communities'), so a small gap remains.

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