Skip to main content
Glama
Sign In

FairSqft Dubai Property Facts

by com.fairsqft
OverviewDiscussionsAdmin

Prepare a Brief Battle request

start_brief
Read-onlyIdempotent

Prepares a Brief Battle request: brokers in the area compete for 72 hours with real units, ranked against DLD fair value. Returns a link the buyer opens to confirm and submit; nothing is sent until the buyer confirms.

Input Schema

NameRequiredDescriptionDefault
areaYesArea name or slug: any of the Dubai areas from list_areas, e.g. "Dubai Marina", "jumeirah-village-circle", "JVC" or "Jumeirah Park". Brief Battle is open in every area.
bedroomsYesMinimum bedrooms: 0 (or "studio") to 7.
timelineNo
financingNo
budget_aedYesMaximum budget in AED.
must_havesNoFree text for brokers. No emails, phone numbers or links.
property_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / area / description
      Previous value: -"Area where Brief Battle runs today: Jumeirah Park, The Springs or The Meadows."New value: +"Area name or slug: any of the Dubai areas from list_areas, e.g. \"Dubai Marina\", \"jumeirah-village-circle\", \"JVC\" or \"Jumeirah Park\". Brief Battle is open in every area."
    • changedInput schema / properties / bedrooms / description
      Previous value: -"Minimum bedrooms."New value: +"Minimum bedrooms: 0 (or \"studio\") to 7."
    • removedInput schema / properties / bedrooms / maximum
      Removed value: -7
    • removedInput schema / properties / bedrooms / minimum
      Removed value: -1
    • changedInput schema / properties / bedrooms / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "string"
+]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description usefully resolves the apparent tension by stating nothing is sent until the buyer confirms, plus the 72-hour window and the returned confirmation link. It does not say whether a pending request object is persisted server-side or whether it can be re-run/expired, which is the remaining gap.

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?

Two tight sentences, with the core mechanic (broker competition) front-loaded and the critical non-commitment guarantee placed last for emphasis. No filler.

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 correctly carries the return-value burden by naming the confirmation link and the buyer-confirm gate. It is largely complete for a 7-parameter initiation tool, though it leaves the optional parameters' effects and any expiry/re-run behavior unexplained.

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

Parameters2/5

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

At 57% schema description coverage, four of the seven parameters (timeline, financing, must_haves, and the enums generally) carry no prose meaning in either place. The description's 'brokers in the area compete' only loosely gestures at the area parameter and adds nothing about budget, bedrooms, or the must_haves restrictions, so it does not compensate for the coverage gap.

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 (prepares) and resource (a Brief Battle request) and immediately explains the mechanic: brokers compete for 72 hours, ranked against DLD fair value. This is unmistakably distinct from the analytics siblings (check_price, estimate_rent, get_comparables), none of which initiate a broker competition.

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?

The description conveys the scenario in which the tool applies (a buyer wanting competing broker offers on real units) and the confirmation step, but never explicitly says when to use this versus check_price or estimate_rent, nor when not to use it. Usage is implied rather than stated.

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

All FairSqft Dubai Property Facts toolsInspect
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