Skip to main content
Glama

Dld Search Rents

dld_search_rents
Read-onlyIdempotent

Dubai rental contracts registered through Ejari with the Dubai Land Department, contract amount, annual amount, start/end dates, area/district, property type and size. Coverage is the current calendar year. A date range is required.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 3,
      "to_date": "2026-09-06",
      "date_type": "0",
      "from_date": "2026-09-01"
    },
    "name": "dld_search_rents"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort as "<COLUMN>_ASC" or "<COLUMN>_DESC" using a column name from the rows, e.g. "TRANS_VALUE_DESC". Omit for the upstream default order.
limitNoRows to return, 1-200 (default 25). Pages above 50 are fetched in slices
usageNoProperty usage: "1" Residential, "2" Commercial, "3" Other
offsetNoRows to skip, for paging through `total` (default 0)
to_dateYesEnd of the range, ISO date e.g. "2026-09-06"
versionNoContract version filter, as seen in VERSION_EN (e.g. New, Renewed)
date_typeNoWhich date the range applies to: "0" registration, "1" contract start, "2" contract end
free_holdNo"1" freehold only, "0" non-freehold only
from_dateYesStart of the range, ISO date e.g. "2026-09-01"
include_arabicNoKeep the Arabic (`*_AR`) twin of each bilingual column. Default false.
property_type_idNoUpstream property-type id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Rows to return, 1-200 (default 25)"New value: +"Rows to return, 1-200 (default 25). Pages above 50 are fetched in slices"
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent, open-world read, so the bar is lower. The description still earns credit by disclosing two real query constraints absent from annotations: results are limited to the current calendar year and a date range is mandatory, both of which materially change how an agent builds requests.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the dataset and followed immediately by the hard constraints, with no filler. The trade-off is that it reads as a noun-phrase data catalog entry rather than an instruction, so the action is implied rather than stated.

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?

With 11 parameters, no output schema, and full schema coverage, the description is adequate: it lists part of the return shape and states the coverage window. It omits that results are paginated via total/offset, that Arabic twin columns exist, and how the multiple property filters interact, leaving gaps an agent would hit at call time.

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 100%, so every parameter including date_type, usage, free_hold, and sort is already documented upstream, making 3 the baseline. The description adds the returned field list (contract amount, annual amount, dates, area, type, size) but gives no extra meaning for the filters, enum choices, or sort syntax.

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 names the specific resource: Ejari-registered Dubai rental contracts from the Dubai Land Department, plus the data fields carried. It lacks an explicit verb and never contrasts itself with the sibling dld_search_transactions, so an agent must infer the rents-vs-sales split from the word "rental" alone.

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

Usage Guidelines2/5

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

The only usage guidance is the constraint "A date range is required," which merely restates the required array. Nothing tells the agent when to pick this tool over dld_search_transactions or dld_search_valuations, and no exclusions or prerequisites are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.