Skip to main content
Glama

Dld List Areas

dld_list_areas
Read-onlyIdempotent

The Dubai Land Department register of area (district) names in English and Arabic with their AREA_ID codes, the reference list behind the AREA_EN values on transaction, rent and valuation rows.

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": {},
    "name": "dld_list_areas"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered by structured data. The description adds meaningful context beyond that — this is a complete reference register of bilingual names and codes rather than a filtered query — but says nothing about result size, ordering, inclusion of retired areas, or response shape.

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?

A single sentence that front-loads the resource and then explains the downstream relevance to AREA_EN values. Both clauses earn their place; the sentence is dense but not padded, and no restructuring is needed.

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, the description carries the burden of describing return content, and it does so by naming the fields returned (English name, Arabic name, AREA_ID). For a zero-parameter list tool with read-only annotations this is nearly sufficient; only scale, ordering, and completeness guarantees are left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to document and the baseline of 4 applies. The description correctly signals a parameterless, whole-register retrieval rather than a search operation.

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 (the Dubai Land Department register of area/district names) and the exact contents (English and Arabic names plus AREA_ID codes). It also situates the tool relative to siblings by calling it 'the reference list behind the AREA_EN values on transaction, rent and valuation rows,' which implicitly distinguishes it from the dld_search_* tools without naming 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?

There is no explicit when-to-use or when-not-to-use statement, but usage is strongly implied: this is the lookup for decoding or resolving AREA_EN values seen on transaction, rent and valuation rows. An agent can infer the call from that relationship, though nothing states prerequisites or that other search tools should be preferred when area codes are already known.

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.