Dubai Wealth Index

Dubai as one picture

get_city_overview

Read-onlyIdempotent

What the index rests on and what it says citywide: counts, median yield, price per square foot, rent and growth, plus the same medians for every area. Use it to pick an area before drilling in, or to state the index's coverage.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`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

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already establish the tool as read-only, idempotent, and non-destructive, so the description only needs to add behavioral context. It adds useful scope expectations—citywide figures plus medians for every area—and implies a coverage statement. However, it does not disclose output shape, potential empty results, or data freshness, so it does not go far beyond annotations.

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 two sentences with no filler. The first sentence front-loads what the tool returns, and the second sentence states practical use cases. Every clause 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?

Given no output schema, the description covers the essential return content and usage intent well. It could be slightly more explicit about how the 'purpose' and 'bedroom' parameters shape the citywide vs. area medians, but the fully documented schema compensates for that gap.

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 input schema documents both parameters fully with enums, defaults, and descriptions, including the important caveat that 'all' is a median rather than a sum. The tool description does not add parameter-specific meaning beyond the schema, so with 100% schema coverage the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the resource as a citywide index overview, listing the statistics returned (counts, median yield, price per square foot, rent and growth) and noting it also covers every area. It positions the tool as a precursor to 'drilling in,' which separates it from more granular area or building tools, though it does not name a sibling explicitly.

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 description gives two specific use cases: 'pick an area before drilling in' and 'state the index's coverage.' This tells the agent when the tool is appropriate, though it does not explicitly state when not to use it or name alternative tools.

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?