Skip to main content
Glama

Heart Homes — Dubai property data

Recent transactions

list_recent_transactions
Read-only

Most recent registered DLD sales or rent contracts for a community or area slug - real records to ground price talk in.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>",
      "kind": "<kind>"
    },
    "name": "list_recent_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes'sale' = DLD sales transactions, 'rent' = Ejari rent contracts
slugYesLocation slug (community or area) as returned by search_locations
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuine provenance value by naming the underlying registries (DLD sales, Ejari rent), but is silent on how far back 'most recent' reaches, the hard 15-record cap, and ordering of results.

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?

A single front-loaded sentence with the resource and scope stated first and zero filler. Every clause (registry names, slug scope, grounding purpose) carries information.

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?

No output schema exists, so the description carries the burden of conveying what comes back, and it never describes the record fields (price, date, area, property type). It also omits the recency window, which matters for a tool whose whole identity is 'most recent'.

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?

At 67% schema coverage the schema already documents the kind enum and that slug comes from search_locations; the description only echoes those mappings. The limit parameter (default 10, max 15) is undocumented in both the schema property and the description, leaving a real gap unbudged.

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?

States a specific resource (registered DLD sales or Ejari rent contracts) scoped to a community/area slug, and 'most recent' implicitly separates it from the historical siblings like get_price_history and get_trends_movers. It stops short of naming any sibling explicitly, so an agent must infer the boundary from context.

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?

'real records to ground price talk in' hints at the use case (citing concrete transactions rather than aggregate stats), which is implied guidance only. There is no explicit when-to-use, when-not-to-use, or named alternative among the twelve siblings.

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.

Resources