Skip to main content
Glama

Dld Search Lands

dld_search_lands
Read-onlyIdempotent

Registered land parcels in Dubai from the Dubai Land Department, parcel and land number, area/district, zone, land type, actual area, project and master project. No date range; filter by land type, zone or project name.

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,
      "land_type_id": "1"
    },
    "name": "dld_search_lands"
  }
}

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
offsetNoRows to skip, for paging through `total` (default 0)
projectNoProject name to match
zone_idNoZone: "1" Deira, "2" Dubai
free_holdNo"1" freehold only, "0" non-freehold only
land_type_idNoLand type: "1" Residential, "2" Agricultural, "3" Industrial, "4" Commercial, "5" Public Facilities, "6" Government Authority
include_arabicNoKeep the Arabic (`*_AR`) twin of each bilingual column. Default false.
master_projectNoMaster-project name to match
property_sub_type_idNoUpstream property-sub-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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered structurally. The description adds the meaningful scoping fact that this dataset is undated, preventing futile date-filter attempts. It says nothing about pagination limits, sort behavior, or result volume, leaving those to the schema.

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?

Two sentences, no filler, with the identifying content front-loaded. The comma-separated field list is dense but functional; it conveys the return shape efficiently rather than padding with boilerplate.

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?

With 10 optional parameters, no required fields and no output schema, the definition does the two things that matter most: it discloses the key output fields so the agent knows what a row contains, and it rules out a whole parameter family (dates). Remaining gaps — sort syntax, include_arabic, free-hold and sub-type semantics — are fully documented in the schema.

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%, including enum labels for zone, land type and freehold, so the baseline is 3. The description restates only land type, zone, project and master-project semantics and adds no format or edge-case guidance beyond the schema.

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 (registered land parcels from the Dubai Land Department) and enumerates the data returned: parcel and land number, area/district, zone, land type, actual area, project, master project. It is distinguishable from siblings such as dld_search_buildings or dld_search_projects by domain, though it never explicitly contrasts itself with them.

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?

It gives a useful negative constraint ('No date range') and names three valid filter axes (land type, zone, project name), which implicitly tells the agent when this tool applies. However, it offers no explicit when-to-use versus alternatives such as dld_search_transactions, so routing still requires inference.

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.