Binayah Dubai Property Data

Ask Binayah to contact someone

send_enquiry

Send an enquiry to Binayah Properties' sales team, who will call or message the person. Only call this when the person has asked to be contacted by Binayah and has given you their name and phone number themselves, in this conversation. Never invent, guess or reuse contact details. The phone must include the country code (e.g. +971 50 123 4567). Limited to 3 enquiries per hour per caller.

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": {
      "name": "<name>",
      "phone": "<phone>",
      "message": "<message>"
    },
    "name": "send_enquiry"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`email`	No
`phone`	Yes	With country code, e.g. +971501234567
`message`	Yes	What they're looking for: area, budget, bedrooms, timing
`project`	No	Project slug or name, if the enquiry is about one
`interest`	No		buy

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Beyond the annotations (openWorldHint=true, idempotentHint=false, destructiveHint=false), it discloses that a human sales team will contact the person, that the call is rate limited to 3 enquiries per hour per caller, and that consent must be given in-conversation. That is meaningful added context; it stops short of saying what a success or failure response looks like.

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?

Four sentences, front-loaded with the action, then the consent gate, then format, then rate limit — every sentence carries an operational constraint. Minor redundancy in restating the phone example already present in the schema.

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?

For a 6-parameter outbound mutation with no output schema and no annotations about permissions, the description covers the highest-risk gaps: consent, contact-data integrity, formatting, and throttling. Only the return/confirmation behavior and the optional fields' purpose remain unexplained.

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 50%, and the description mostly reinforces what is already in the schema (phone country-code requirement with an example is nearly verbatim from the schema). It adds real meaning for name/phone (must be self-supplied in this conversation) but says nothing about email, project, or the interest enum/default.

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 verb and resource ('Send an enquiry to Binayah Properties' sales team') plus the downstream outcome ('who will call or message the person'). It is implicitly distinguishable from the read-only siblings (area_prices, project_price_check, search_projects) by being the only outbound-contact action, but it never explicitly contrasts itself with them.

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

Usage Guidelines5/5

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

Gives an explicit precondition ('Only call this when the person has asked to be contacted ... and has given you their name and phone number themselves, in this conversation') and an explicit prohibition ('Never invent, guess or reuse contact details'). This is exactly the when/when-not guidance an agent needs for a consent-sensitive action.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Binayah Dubai Property Data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?