Skip to main content
Glama

Dld List Brokers

dld_list_brokers
Read-onlyIdempotent

Licensed real-estate brokers on the Dubai Land Department register, broker number and name, licence start/end dates, the brokerage office they sit under, and the office phone published on the register.

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,
      "gender": "1"
    },
    "name": "dld_list_brokers"
  }
}

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
genderNoRegistered gender: "0" male, "1" female. Omit for all.
offsetNoRows to skip, for paging through `total` (default 0)
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

C2.8/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. The description adds that data is drawn from a public DLD register (including published office phone), which usefully frames the data source, but says nothing about result volume, paging, or completeness despite the schema exposing limit/offset and sliced fetching above 50 rows.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One compact sentence with no padding, and the resource is stated first. However, it is a dangling fragment rather than a complete statement, and the trailing field enumeration reads like a data dictionary rather than guidance.

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 no output schema, the field list is the only description of what comes back, which is genuinely useful. But for a paged list tool it omits any mention of the total/paging model and gives no framing of how large the register is, leaving an agent to rely entirely on the schema for operational behavior.

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%, with each of the five parameters documented including the enum for gender and the sort format, so the baseline is 3. The description contributes nothing about sorting, paging, or the Arabic-column toggle beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun fragment with no verb, but the resource is unambiguous: licensed brokers on the Dubai Land Department register, with the specific fields returned. It implicitly distinguishes itself from sibling registries (areas, developers, buildings) by naming the broker domain, though it never states an action such as 'list' or 'retrieve'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. An agent gets no signal about whether this is the right tool for a broker lookup versus a building/transaction search, and nothing about when the register data would or would not apply.

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.