Dubai Wealth Index

Every published building in an area

get_area

Read-onlyIdempotent

One Dubai area: its own medians, its medians by bedroom type, and every building it publishes ordered by gross yield with unpublishable yields last rather than hidden. Also lists buildings that trade but sit below the publication gate, so the set is never mistaken for the whole market.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`area`	Yes
`bedroom`	No	"all" is the building- or area-wide median, not a sum of the rest.	all
`purpose`	No	Which market to read. A building may publish one and not the other.	sale
`buildingLimit`	No

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already establish this is read-only and idempotent. The description adds non-obvious behavioral detail: unpublishable yields appear last rather than being hidden, and below-publication-gate buildings are included so the set is not mistaken for the whole market. This significantly reduces misinterpretation risk.

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 front-load the area scope and pack in the ordering and inclusion caveats without unnecessary repetition. Both sentences earn their place by clarifying output behavior rather than restating the schema.

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

Completeness3/5

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

The description is conceptually rich, covering medians, sorted buildings, and below-gate trades. However, there is no output schema, no return shape is described, and the interaction between 'every building' and the buildingLimit parameter is unaddressed, which could mislead an agent about pagination or truncation.

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 description coverage is 50%, and the description adds some meaning by tying 'medians by bedroom type' to the bedroom parameter and 'One Dubai area' to the area parameter. However, it adds little for the purpose or buildingLimit parameters, and 'every building it publishes' is left unqualified against the default buildingLimit of 50.

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 names the exact scope ('One Dubai area'), the resources returned (medians, medians by bedroom type, every published building), and the ordering rule (by gross yield). This clearly distinguishes it from siblings like get_building (single building) and get_city_overview (city-wide).

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 opening 'One Dubai area' and the title 'Every published building in an area' make the intended use clear: an area-level snapshot of published buildings and medians. It does not explicitly name alternatives or exclusion conditions, but the context is strong enough for an agent to select it correctly.

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?