Skip to main content
Glama

Binayah Dubai Property Data

Check a Dubai listing's price

deal_check
Read-only

Run Binayah's Deal Check on one Dubai property listing from any agency: paste the listing text, or give the listing URL. Compares the asking price with registered sales of comparable homes (or, for a rental, with registered rent contracts) and gives a verdict, the price comparison, a confidence level and the headline cash needed. The full report (cost breakdown, questions to ask, alternatives) is on binayah.ae/deal-check. Not a valuation and not financial advice. Takes up to about 40 seconds. Limited to 8 checks per 10 minutes per caller.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "deal_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoListing URL (portal pages sometimes block reading; then paste the text)
textNoThe listing text: price, size, bedrooms, community, building
mortgageNoBuyer plans to use a mortgage

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only cover readOnly and openWorld, but the description adds substantial operational detail beyond them: ~40 second runtime, an explicit rate limit of 8 checks per 10 minutes per caller, and the caveat that portal URLs sometimes block reading (fall back to pasting text). It also discloses what the response contains (verdict, price comparison, confidence, headline cash needed) and where the fuller report lives.

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?

Purpose and input options are front-loaded, then results, then caveats, runtime and limits. Every sentence carries information; the only mild bloat is the marketing pointer to binayah.ae/deal-check, which is still useful for the agent to know a truncated summary is returned.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the burden of describing returns, and it does: verdict, price comparison, confidence level, headline cash needed, with the full breakdown elsewhere. Runtime, rate limits, input fallbacks and scope limits are all covered for a three-parameter, zero-required tool.

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 the schema already explains url, text and mortgage. The description adds only indirect meaning (the 'for a rental' clause implies rental vs. sale is inferred from the listing text) and never mentions the mortgage parameter, so it neither compensates nor misleads. Baseline 3 is appropriate.

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

Purpose5/5

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

States a specific verb and resource ('Run Binayah's Deal Check on one Dubai property listing') and then spells out the actual computation: asking price vs. registered sales of comparable homes, or registered rent contracts for a rental. This clearly separates it from sibling tools like area_prices or project_price_check, which operate at area/project level rather than on a single listing.

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

Usage Guidelines4/5

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

Gives clear selection context ('one Dubai property listing from any agency') and two input routes (paste text or give URL), plus a scope exclusion ('Not a valuation and not financial advice'). It does not explicitly name when to prefer a sibling such as project_price_check for a new-build unit, so routing is clear but not exhaustively disambiguated.

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