Skip to main content
Glama

Dld Search Transactions

dld_search_transactions
Read-onlyIdempotent

Dubai property transactions (sales, mortgages and gifts) registered with the Dubai Land Department, with transaction value, procedure, area/district, project, property type, room count and nearest metro/mall/landmark. Coverage is the current calendar year, earlier years come back empty. 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": {
      "sort": "TRANS_VALUE_DESC",
      "limit": 3,
      "to_date": "2026-09-06",
      "from_date": "2026-09-01",
      "transaction_type": "1"
    },
    "name": "dld_search_transactions"
  }
}

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. Omit for all.
offsetNoRows to skip, for paging through `total` (default 0)
to_dateYesEnd of the range, ISO date e.g. "2026-09-06"
off_planNo"1" off-plan only, "0" ready only
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, as seen in PROPERTY_TYPE_ID
transaction_typeNoGroup: "1" Sales, "2" Mortgages, "3" Gifts. Omit for all.

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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds the non-obvious behavioral fact that only the current calendar year is indexed and earlier years return empty, plus what data each row carries. It omits return-format and paging behavior (the schema covers those), which keeps it just short of top marks.

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 tight sentences, front-loaded with the entity and its payload, then the coverage caveat. The final sentence ('A date range is required') is redundant with the schema's required list and is the one line that does not earn its place outright.

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?

For an 11-parameter, no-output-schema search tool, the definition covers the essentials: what entity, what fields come back, the required date range, and the sharp coverage limitation that would otherwise cause empty-result confusion. It would be fully complete with a note on default ordering or result-set paging, but nothing critical for a correct call is missing.

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 all 11 parameters—including sort syntax, limit range, offset, enums for usage/off_plan/free_hold/transaction_type—are already documented. The description only restates that a date range is required, adding no syntax, interaction, or format detail beyond the schema; the baseline 3 applies.

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 (search) and resource (Dubai Land Department property transactions) and enumerates both the transaction categories (sales, mortgages, gifts) and the returned fields (value, procedure, area/district, project, property type, room count, nearest metro/mall/landmark). This makes it trivially distinguishable from siblings such as dld_search_buildings, dld_search_lands and dld_search_rents 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 Guidelines3/5

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

The description supplies a hard usage constraint ('A date range is required') and a critical coverage boundary ('current calendar year, earlier years come back empty'), which tells the agent when this tool will and will not yield results. However, it gives no explicit guidance on when to prefer this over sibling searches (e.g. rents, valuations) or how to combine it with them, so usage is largely implied.

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.