Dubai Wealth Index

The transactions behind the medians

get_building_transactions

Read-onlyIdempotent

The individual registered transactions a building's medians rest on. Use it to check whether a median rests on many comparable sales or a few scattered ones. Rent rows exist only where rent was measured at building grain, and transaction rows are not snapshot-versioned — both caveats are returned with the data and must be repeated when quoting it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`area`	Yes
`building`	Yes
`windowMonths`	No

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already mark the tool read-only and idempotent, and the description adds meaningful caveats beyond that: rent rows exist only at building grain and transaction rows are not snapshot-versioned. It also notes these caveats must be repeated when quoting the data, which is valuable non-obvious behavioral context.

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 sentences with no filler. The purpose, use case, and important caveats are all front-loaded and each sentence 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?

The description gives a clear purpose, explicit use case, and critical data caveats even without an output schema. The main gap is the lack of parameter semantics, but overall the definition is well-rounded for a read-only, idempotent transaction lookup tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain area, building, or windowMonths. The schema patterns and const values provide some intrinsic meaning, but the description adds no parameter-level guidance, so it fails to compensate for the coverage 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: it returns the individual registered transactions underlying a building's medians. This clearly separates it from sibling tools like get_building or get_ranking, and the title reinforces the purpose.

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 says when to use the tool: to check whether a median rests on many comparable sales or a few scattered ones. It does not name alternatives or state when not to use it, but the use case is clear enough for an agent to route 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?