Dubai Wealth Index

Search the index

search

Read-onlyIdempotent

Find a building, area or project by name. Matching is trigram-based, so a half-remembered or misspelled name still resolves. Every hit links to a page that exists — buildings below the publication gate are never returned. Call this first when a question names a place, then pass a hit's id to fetch for the whole record, or its slugs to get_building or get_area for the figures alone.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	Yes
`results`	Yes
`dataAsOf`	Yes

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description adds meaningful behavior: trigram-based fuzzy matching and the publication-gate filter ensuring results always link to existing pages. This gives the agent expectations for recall and result validity.

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 dense sentences with no filler. The first sentence states purpose, the second adds behavioral context, and the third provides workflow guidance. Every clause contributes meaning.

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?

The description is complete for this tool's simplicity: it explains what is searched, how matching behaves, what results guarantee, and how responses should be chained to sibling tools. The annotations cover safety and idempotence, and an output schema exists, so return-value documentation is not required.

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?

The input schema has 0% description coverage, so the description compensates for the key 'query' parameter by explaining it is a name and that matching tolerates misspellings. The optional 'limit' parameter is not explained in prose, but its schema constraints (default 8, max 20) make it self-explanatory.

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-resource pair: 'Find a building, area or project by name.' It clearly distinguishes this search tool from the sibling fetch/get_building/get_area tools by explaining that search resolves names and then hands off IDs or slugs to those siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit routing guidance: 'Call this first when a question names a place', then explains the follow-up steps to fetch or get_building/get_area. This makes it obvious when to use search versus the alternatives.

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?