Skip to main content
Glama

Dld Search Buildings

dld_search_buildings
Read-onlyIdempotent

Registered buildings in Dubai from the Dubai Land Department, building number, floors, rooms, flats/shops/offices counts, actual area, area/district, zone, project and creation date. No date range needed; filter by zone, freehold, leasehold or off-plan status.

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,
      "zone_id": "1"
    },
    "name": "dld_search_buildings"
  }
}

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)
zone_idNoZone: "1" Deira, "2" Dubai
off_planNo"1" off-plan only, "0" ready only
free_holdNo"1" freehold only, "0" non-freehold only
lease_holdNo"1" leasehold only, "0" non-leasehold only
include_arabicNoKeep the Arabic (`*_AR`) twin of each bilingual column. Default false.

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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds the useful note that no date range is required, but says nothing about result volume, paging behavior, or what is omitted when include_arabic is false.

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?

Two compact sentences with the resource and the returned fields front-loaded, followed by the filtering mode. No filler or repeated phrasing.

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 no output schema, enumerating the returned fields in the description does the job of explaining results. Eight optional parameters are fully documented in the schema, so the definition is largely self-sufficient, though paging and the meaning of 'total' are left to 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% and each parameter already carries enum meanings and defaults, so the baseline is 3. The description only restates the filter categories (zone, freehold, leasehold, off-plan) without adding semantics 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?

Names the specific resource (registered buildings from Dubai Land Department) and enumerates the fields returned (building number, floors, rooms, flat/shop/office counts, area, zone, project, creation date). It is clearly distinguishable from dld_search_lands or dld_search_transactions by resource, though it never explicitly contrasts 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?

'No date range needed; filter by zone, freehold, leasehold or off-plan status' gives real usage context and implicitly contrasts with date-bounded siblings like transaction searches. However it offers no explicit when-not guidance or named alternative for related lookups (e.g., projects or areas).

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.