Evlek — Northern Cyprus Property MCP Server

Official

by Evlek

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

Get Full Detail for a Single Evlek Listing

get_listing_detail

Read-only

Get a full 360° profile for any active Evlek listing by UUID or listing number: title, price, location, size, amenities, photos, and AI staging.

Instructions

Return a 360° profile of one active Evlek listing by UUID or listing number: title, description, price, location, size, amenities, features, cover image, per-photo captions/tags, and AI virtual-staging before/after pairs (always AI-disclosed). Contact details omitted. Use when: a UUID or listing number is already known. Don't use for: discovery — use search_listings first. The legacy property_id parameter name is still accepted as an alias of propertyId.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`propertyId`	Yes	Evlek listing UUID or listing number (e.g. "EVL-123456", "123456")

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No
`url`	No
`city`	No
`type`	No
`found`	Yes
`price`	No
`title`	No
`photos`	No
`areaSqm`	No
`fxRates`	No
`bedrooms`	No
`currency`	No
`district`	No
`factType`	No
`features`	No
`listedAt`	No
`priceGbp`	No
`amenities`	No
`bathrooms`	No
`furnished`	No
`dataSource`	No
`isEstimate`	No
`photoCount`	No
`photosShown`	No
`coverImageUrl`	No
`listingNumber`	No
`monthlyRentGbp`	No
`pricePerSqmGBP`	No
`virtualStaging`	No
`photosTruncated`	No
`locationPrecision`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedv2.1.0Sep 14, 2026

addedInput schema / properties / propertyId

Added value: +{
+  "description": "Evlek listing UUID or listing number (e.g. \"EVL-123456\", \"123456\")",
+  "type": "string"
+}

removedInput schema / properties / property_id

Removed value: -{
-  "description": "Evlek listing UUID",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "property_id"
-]New value: +[
+  "propertyId"
+]

addedOutput schema / properties / dataSource
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / factType
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / fxRates

Added value: +{
+  "properties": {
+    "base": {
+      "enum": [
+        "GBP"
+      ],
+      "type": "string"
+    },
+    "isFallback": {
+      "type": "boolean"
+    },
+    "rates": {
+      "properties": {
+        "EUR": {
+          "type": "number"
+        },
+        "TRY": {
+          "type": "number"
+        },
+        "USD": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "EUR",
+        "USD",
+        "TRY"
+      ],
+      "type": "object"
+    },
+    "source": {
+      "enum": [
+        "database",
+        "fallback"
+      ],
+      "type": "string"
+    },
+    "updatedAt": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "base",
+    "rates",
+    "source",
+    "updatedAt",
+    "isFallback"
+  ],
+  "type": [
+    "object",
+    "null"
+  ]
+}

addedOutput schema / properties / isEstimate
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / locationPrecision

Added value: +{
+  "enum": [
+    "exact",
+    "district",
+    "city"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / monthlyRentGbp

Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / photosShown
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / photosTruncated
```
Added value: +{
+  "type": "number"
+}
```

removedOutput schema / properties / titleDeedBand

Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}

removedOutput schema / properties / titleDeedLabel

Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}

removedOutput schema / properties / titleDeedType

Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}

addedOutput schema / properties / virtualStaging

Added value: +{
+  "properties": {
+    "available": {
+      "type": "boolean"
+    },
+    "disclosure": {
+      "type": "string"
+    },
+    "items": {
+      "items": {
+        "properties": {
+          "afterUrl": {
+            "type": "string"
+          },
+          "beforeUrl": {
+            "type": "string"
+          },
+          "provenance": {
+            "properties": {
+              "digitalSourceType": {
+                "type": "string"
+              },
+              "generatedAt": {
+                "type": "string"
+              },
+              "humanReview": {
+                "type": "string"
+              },
+              "kind": {
+                "type": "string"
+              },
+              "model": {
+                "type": "string"
+              },
+              "modelVersion": {
+                "type": "string"
+              },
+              "originalRetained": {
+                "type": "boolean"
+              },
+              "outputId": {
+                "type": "string"
+              },
+              "outputSha256": {
+                "type": "string"
+              },
+              "provider": {
+                "type": "string"
+              },
+              "version": {
+                "type": "number"
+              },
+              "visibleDisclosureApplied": {
+                "type": "boolean"
+              }
+            },
+            "type": "object"
+          },
+          "roomType": {
+            "type": "string"
+          },
+          "style": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / required
```
Added value: +[
+  "found"
+]
```

First observedv1.6.0Jul 30, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=true, destructiveHint=false), the description discloses meaningful behaviors: contact details are omitted, AI virtual-staging is always disclosed, and only active listings are returned. These details inform an agent about content boundaries and policy compliance beyond what the annotations or schema state.

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?

The description is information-dense but every clause earns its place: main behavior, field list, exclusions, usage guidance, and alias note. It is front-loaded with the core purpose and avoids redundant restatement of the title.

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?

For a single-parameter, read-only tool with an output schema present, the description covers everything an agent needs: what is returned, what is omitted, when to use it, and how to identify the listing. No critical gaps remain.

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 coverage is 100%, so the schema already documents the parameter well. The description adds value by clarifying that the propertyId can be a UUID or listing number and by noting the legacy 'property_id' alias is still accepted, which the schema does not mention.

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?

The description uses a specific verb and resource: 'Return a 360° profile of one active Evlek listing by UUID or listing number,' followed by a concrete list of included fields. It clearly distinguishes itself from discovery-oriented tools by naming search_listings as the alternative, making its role unambiguous.

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?

Explicit guidance is provided: 'Use when: a UUID or listing number is already known. Don't use for: discovery — use search_listings first.' This gives both positive and negative usage conditions and names the exact alternative, leaving no inference required.

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

Deploy Server