Dubai Wealth Index

One building's record

get_building

Read-onlyIdempotent

The full record for one apartment building: median registered sale prices, registered rents, gross yield and the basis it was computed on, growth, turnover upside, off-plan uplift and the forward short-let rate curve where one exists — all by bedroom type. Medians of registered Dubai Land Department sales and Ejari contracts, never asking prices. Identical to the site's public JSON record.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`area`	Yes
`purpose`	No	Which market to read. A building may publish one and not the other.	sale
`building`	Yes
`includeMonthly`	No	The monthly series. Long — omit unless the question is about a trend.

TDQS

A4/5.0

Behavior4/5

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

Annotations already establish read-only and idempotent behavior. The description adds meaningful context beyond that: data comes from registered DLD sales and Ejari contracts, not asking prices, and some series exist only conditionally. This gives an agent useful expectations beyond the annotation hints.

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 dense sentences convey scope, contents, data source, and conditionality without filler. The main purpose is front-loaded, and the source clarification 'never asking prices' earns its place.

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?

For a read-only retrieval tool with no output schema, the description gives a strong picture of what the response contains and where the data originates. Minor omissions like parameter format or behavior when a building has no record are non-critical given the simple input schema.

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?

The schema documents purpose and includeMonthly with descriptions, and the tool description reinforces the sale/rent distinction by mentioning both sale prices and rents. However, the required area and building parameters are left unexplained, and the description does not add enough detail to fully compensate for that gap.

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 states a specific verb and resource: getting the full record for one apartment building. It names concrete fields (median sale prices, rents, gross yield, growth, turnover upside, off-plan uplift, short-let curve), which clearly distinguishes it from siblings like get_building_transactions and get_area.

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 intended use is implied clearly: call this when you need the complete aggregated record for one building. However, it never explicitly contrasts it with get_building_transactions or other siblings, nor states when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Dubai Wealth Index tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool targets a distinct resource and action: fetch retrieves any full record by id or URL, get_area handles area-level medians, get_building gives building records, get_building_transactions lists underlying transactions, get_city_overview provides citywide scope, get_methodology explains definitions, get_ranking returns a single sorted ranking, get_villa_community focuses on villa communities, list_favorites accesses account-specific data, list_rankings enumerates available rankings, and search resolves names to ids. No two tools have overlapping purposes, even when addressing similar domains (e.g., list_rankings vs. get_ranking are clearly differentiated by singular vs. plural and availability of methods).

Naming Consistency5/5

All tool names use a consistent lowercase_with_underscores format and follow a clear verb_noun pattern: get_ for retrieving specific entities, list_ for enumerations, search for lookup, and fetch for generic retrieval. This makes the API predictable and easy to navigate.

Tool Count5/5

With 11 tools, the server is well-scoped for a real estate index covering city, areas, buildings, villas, transactions, rankings, methodology, and account favorites. Each tool serves a unique function without unnecessary redundancy, fitting the typical range for a purpose-built data server.

Completeness5/5

The tool set provides comprehensive coverage for a read-only data server: search, area and building details, transaction histories, citywide overview, rankings and their methods, villa communities, methodology reference, and saved favorites. There are no obvious gaps—users can navigate from search to specific records, drill into transactions, compare rankings, and retrieve the methodology behind any figure.

Resources

Need Help?