Skip to main content
Glama

Heart Homes — Dubai property data

Building statistics

get_building_stats
Read-only

Stats for one building: 12-month sales, median price, trend, recent sales, property-type mix, and - where rent contracts can be attributed to the building - median annual rent and recent rent contracts, and a per-bedroom rent breakdown where enough contracts resolve a bedroom. Takes the communitySlug + buildingSlug pair returned by search_locations.

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>",
      "buildingSlug": "<buildingSlug>"
    },
    "name": "get_building_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
buildingSlugYes
communitySlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds valuable data-availability behavior: rent figures appear only when contracts can be attributed to the building, and bedroom breakdowns only where enough contracts resolve a bedroom.

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?

The description is a single front-loaded sentence that starts with the core purpose before listing return dimensions and conditional caveats. Every clause adds useful information, and there is no repetitive or empty phrasing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries responsibility for explaining returns, and it does so comprehensively: sales history, median price, trend, recent sales, property-type mix, rent metrics, and per-bedroom rent. Combined with annotations covering safety and the explicit parameter source, an agent has enough to invoke it correctly.

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 description coverage is 0%, so the schema itself gives only string constraints and no semantic meaning. The description compensates by naming both parameters as slugs and identifying their source, the pair returned by search_locations, though it does not describe slug format or validation beyond that.

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?

The description opens with a specific verb-and-resource phrase, 'Stats for one building,' and then enumerates the exact dimensions returned. This clearly distinguishes it from broader siblings like get_location_stats or get_market_overview by scoping the result to a single building.

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?

It explicitly tells the agent where the required identifiers come from: the communitySlug + buildingSlug pair returned by search_locations. It does not explicitly contrast this tool with get_location_stats or rank_buildings, so the when-to-use guidance is strong 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