Skip to main content
Glama
Sign In

BrokersLynk — Abu Dhabi property market

by io.github.BrokersLynk
OverviewDiscussionsAdmin

abu_dhabi_market

Live property market figures for an area of Abu Dhabi from BrokersLynk: how many live listings brokers offer for 1-, 2- and 3-bed homes to buy and to rent, what the middle half of them ask, example homes (building, beds, price — never contact details), how many buyers and tenants are looking, and a link that opens the same search on brokerslynk.com, and a link that opens a WhatsApp chat with a BrokersLynk broker. Areas: Al Reem Island, Yas Island, Saadiyat Island, Al Raha Beach, Masdar City, Al Reef, Khalifa City. Without an area, every area.

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": "abu_dhabi_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoAn area name from the list, or its slug (e.g. yas-island).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it describes the returned data, notes example homes never include contact details, and mentions live figures and links. It does not cover authentication, rate limits, or error behavior, but for a read-only market-data tool this is reasonably transparent.

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?

The description is front-loaded with the core purpose and every clause describes relevant output or input behavior. It is somewhat long and runs as a single dense sentence, but it is not padded with irrelevant content.

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?

Since there is no output schema, the description appropriately explains the return contents in detail, including counts, price ranges, example homes, demand figures, and links. It is nearly complete for an agent to invoke the tool correctly, though it omits sibling-tool routing guidance.

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?

Schema coverage is 100% and the schema documents the area parameter, but the description adds meaningful semantics: it enumerates the valid area names and states that omitting the area returns every area. This is useful value beyond the schema.

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 clearly states the resource and scope: live property market figures for Abu Dhabi areas from BrokersLynk, including listing counts, asking prices, example homes, buyer/tenant demand, and links. It is specific enough to distinguish from a generic search tool, but it does not explicitly differentiate itself from the sibling brokerslynk_search_link.

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?

It explains the optional area parameter and the default behavior (all areas when omitted) and lists supported areas. However, it gives no explicit guidance on when to use this tool versus brokerslynk_search_link, leaving that choice to inference.

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

All BrokersLynk — Abu Dhabi property market 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