MRK Dubai Property

get_rent_cap_increase

Calculate the maximum legal rent increase in Dubai per RERA Decree 43/2013 rent cap tiers based on how far current rent is below market average.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "currentRentAed": "<currentRentAed>",
      "marketAverageAed": "<marketAverageAed>"
    },
    "name": "get_rent_cap_increase"
  }
}

Input Schema

Name	Required	Description	Default
`currentRentAed`	Yes	Current annual rent in AED
`marketAverageAed`	Yes	Market average annual rent in AED

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are supplied, so the description must carry behavioral burden, and it does add real value by citing the legal basis (RERA Decree 43/2013) and the tiering logic driven by the gap to market average. However, it never states the shape of the result (percentage cap vs AED amount vs tier label) or the edge case where current rent already equals or exceeds market average, which matters for a no-annotation, no-output-schema calculator.

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?

A single sentence with zero filler, front-loading the verb, the jurisdiction, and the governing regulation before the computation basis. Nothing is redundant or buried.

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?

For a two-parameter deterministic calculator this is close to sufficient and the inputs are fully specified. Because there is no output schema, the description should say what the caller receives (percentage, AED figure, or tier), and it is silent on inputs outside the expected regime, leaving a meaningful 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?

Schema coverage is 100% and both parameters are documented as annual AED amounts, so the baseline is 3. The description adds only the relational insight that the two values are compared as a gap, which is modest value beyond what the schema already conveys.

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?

States a specific verb ('Calculate') and a precisely scoped resource ('maximum legal rent increase in Dubai per RERA Decree 43/2013 rent cap tiers'), and names the determining factor. This is clearly separable from sibling calculators such as calculate_mortgage or calculate_purchase_costs without opening any schema.

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 establishes the applicability condition implicitly and clearly: it applies when a tenant/landlord wants the RERA-capped increase given current rent versus market average. It does not explicitly name alternatives or exclusions (e.g. what to do for non-residential or non-Dubai leases), keeping it below a 5.

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

All MRK Dubai Property tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?