Skip to main content
Glama

Dld List Developers

dld_list_developers
Read-onlyIdempotent

Real-estate developers registered with the Dubai Land Department, developer number and name, licence dates and contact details. A date range is required and is matched against the licence dates.

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

Input Schema

NameRequiredDescriptionDefault
nameNoDeveloper name to match
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)
to_dateYesEnd of the range, ISO date e.g. "2026-09-06"
from_dateYesStart of the range, ISO date e.g. "2026-09-01"
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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds one genuinely new behavioral fact beyond that: the required date range is matched against licence dates, not registration or transaction dates. It says nothing about result volume, paging behavior, or the ordering default.

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 tight sentences with no filler; the resource definition comes first and the hard constraint second. Nothing needs to be cut, though the first sentence is a fragment rather than a front-loaded verb phrase.

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 full schema coverage, four safety annotations and no output schema, the description carries only a modest burden and mostly meets it. It is thin on what a returned row looks like beyond a partial field list, and omits any note on paging through `total` or the sliced fetch behavior flagged in the limit parameter.

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 seven parameters are documented inline, making 3 the baseline. The description contributes only the semantic detail that from_date/to_date bind to licence dates — useful, but it does not extend to name matching behavior, sort column expectations, or the include_arabic flag.

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 developers registered with the Dubai Land Department) and the fields it returns (developer number, name, licence dates, contact details), so an agent can tell it apart from dld_list_brokers or dld_list_areas. It lacks an explicit verb and never names a sibling, so it stops short of a 5.

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 states a real usage constraint — a date range is required and is matched against licence dates — which tells the agent it cannot call this unfiltered. It gives no guidance on when to prefer this over the sibling list/search tools, leaving that inference to the agent.

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.