Skip to main content
Glama

Dld Search Projects

dld_search_projects
Read-onlyIdempotent

Real-estate development projects registered with the Dubai Land Department, developer, project status, percent complete, start/completion dates and location. A date range AND a date_type are both required; without date_type the upstream returns nothing.

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": "1",
      "from_date": "2026-08-01"
    },
    "name": "dld_search_projects"
  }
}

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)
statusNoProject status
to_dateYesEnd of the range, ISO date e.g. "2026-09-06"
zone_idNoZone: "1" Deira, "2" Dubai
date_typeYesWhich project date the range applies to: "1" start, "2" end, "3" adoption, "4" completion
from_dateYesStart of the range, ISO date e.g. "2026-09-01"
include_arabicNoKeep the Arabic (`*_AR`) twin of each bilingual column. Default false.
project_type_idNoUpstream project-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.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered. The description adds genuine upstream behavior an agent could not otherwise know — silence on date_type yields an empty result — plus the shape of the returned record set, which substitutes for the absent output 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 critical date_type constraint placed at the end of a short block where it is easy to catch. The first sentence is a bare noun phrase without a verb, which slightly weakens the front-loading but costs no words.

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 a 10-parameter search tool with full schema coverage, the description covers the resource, the returned fields and the one hard failure mode. Since no output schema exists, listing returned attributes is the right compensating move; only cross-sibling disambiguation 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 every parameter including sort, limit, zone_id, project_type_id and include_arabic is already documented upstream. The description only reinforces the required-ness of from_date/to_date/date_type, which the schema's 'required' array already states; no extra syntax or format meaning is contributed.

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 a specific resource — real-estate development projects registered with the Dubai Land Department — and enumerates the fields returned (developer, status, percent complete, dates, location). It lacks an explicit verb, but the resource noun ('projects') distinguishes it implicitly from siblings like dld_search_buildings, dld_search_lands and dld_search_transactions.

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 one strong usage constraint: a date range AND date_type are both required, and without date_type the upstream returns nothing. However, it offers no guidance on when to prefer this over the other dld_search_* siblings or what to do if the required window is unknown, so usage is implied rather than routed.

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.