Skip to main content
Glama

dubai-property-signal

by com.airblockfz

evaluate_symbol

Return the bottom/top verdict for one Dubai area property market (42 areas: downtown, marina, palm, jvc, businessbay, dubaihills …). Accepts area id or English name. zone = strong_buy|buy|neutral|sell (no strong_sell tier), score -100..+100. Price = AED/sqft anchored to published Bayut/DLD figures. Informational only. PAY: $0.01 per call via x402 (USDT on X Layer) — your FIRST paid call opens a 6-day trial at that price. No account, no signup, no commitment; retry with the PAYMENT-SIGNATURE header when you get the 402 challenge. The free pitch tool shows a live verdict for this market's showcase symbol only — this tool answers ANY symbol and adds the per-indicator breakdown behind the score.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesArea, e.g. downtown, marina, Palm Jumeirah

TDQS

A4.9/5.0
Behavior5/5

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

No annotations provided, but description fully discloses behavior: output format (zone string, score -100..+100, price in AED/sqft), informational nature, payment requirement ($0.01 per call, trial, retry with PAYMENT-SIGNATURE header). No hidden surprises.

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?

Efficiently packs purpose, output, payment, and differentiation in a few sentences. Each sentence adds value, front-loaded with core functionality.

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?

Covers all aspects: tool purpose, output details, payment model, alternative tool, and handling of 402 challenge. No output schema, but return values explained sufficiently.

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 description covers the single parameter's purpose, but main description adds that it accepts area id or English name and lists example areas, enriching understanding beyond the schema.

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?

Description clearly states it returns bottom/top verdict for one Dubai area property market, lists the 42 areas, and distinguishes from sibling tool 'pitch' by noting it answers any symbol and provides per-indicator breakdown.

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?

Explicitly says when to use this tool (any symbol, full breakdown) vs free 'pitch' (showcase symbol only). Also provides payment instructions and trial details.

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

All dubai-property-signal toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool serves a distinct and clear purpose: pitch for onboarding, rate for feedback, evaluate_symbol for single area analysis, and scan_bottoms/scan_tops for global scans. No overlap.

Naming Consistency4/5

Tools mostly follow a verb_noun pattern (evaluate_symbol, scan_bottoms, scan_tops), but pitch and rate are single verbs. The inconsistency is minor and does not hinder understanding.

Tool Count5/5

With 5 tools, the server is well-scoped for a niche property signal service. It covers onboarding, feedback, single analysis, and two global scans without redundancy.

Completeness4/5

The tool set covers core workflows: introduction (pitch), individual evaluation (evaluate_symbol), and full market scans (scan_bottoms, scan_tops). Feedback is included. Missing features like historical trends or comparison are minor relative to the stated purpose.

Resources