Skip to main content
Glama

Heart Homes — Dubai property data

Buy vs rent comparison

compare_buy_vs_rent
Read-only

Compare buying vs renting in one community or area: 12-month weighted median sale price, median annual rent, and the implied gross rental yield. 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": "compare_buy_vs_rent"
  }
}

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/5.0
Behavior4/5

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

Annotations already cover the read-only, non-destructive, closed-world profile, and the description layers on genuine computation detail: the 12-month weighting window, that rent is annualized, and that yield is gross and implied. It stops short of stating data recency, currency, or confidence caveats, so the disclosure is helpful but not complete.

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?

One front-loaded sentence delivers the verb, the resource, the full metric set, and the optional filter with no filler. Nothing is buried and nothing needs cutting.

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 usefully compensates by naming the returned fields, and with only one required parameter plus a covered enum, calling it correctly is low-risk. What remains unexplained is the units/currency of price and rent and the reference period for the 12-month window.

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%, so slug and propertyClass are fully documented in the schema; baseline is 3. The description's contribution ('one community or area', 'optionally filter') only restates cardinality and optionality already implied by the schema, adding no format or edge-case guidance.

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 and resource ('Compare buying vs renting in one community or area') and enumerates the exact derived metrics returned: 12-month weighted median sale price, median annual rent, implied gross rental yield. That output framing distinguishes it from stats-only siblings like get_location_stats or rank_communities without needing to name them.

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?

'Optionally filter to one property class' is the only conditional guidance offered; there is no statement of when to prefer this over get_location_stats, check_asking_price, or check_asking_rent despite heavy overlap in domain. Usage is inferable from the purpose but not routed.

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