Evlek — Northern Cyprus Property MCP Server

Official

by Evlek

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

Search Northern Cyprus Property Listings

search_listings

Read-only

Search live Northern Cyprus property sale and rent listings. Filter by city, type, price, and features like pool or garden to see current asking prices and listing facts.

Instructions

Search live active sale and long-term-rent listings on Evlek. Results are newest-first by default; limit caps returned rows and totalMatched reports the full match count. Returns advertised asking-price and listing facts only; not valuation, verification of property-specific claims, forecast, ranking, or recommendation.

Input Schema

TableJSON Schema

Name	Required	Description
`city`	No	Slug, Turkish name, or exonym (Kyrenia/Nicosia/Famagusta/Morphou).
`pool`	No	Only listings with a pool
`type`	No	Listing type
`limit`	No	Result count (integer 1-10, default 5)
`garden`	No	Only listings with a garden
`offset`	No	Rows to skip (pagination, default 0)
`sortBy`	No	Sort order (default: newest)
`parking`	No	Only listings with parking
`seaView`	No	Only listings flagged sea_view
`bedrooms`	No	Bedroom count (integer 0-10)
`district`	No	District name (e.g. Alsancak), matched accent/case-insensitively against the active-listing district list
`elevator`	No	Only listings with an elevator
`maxPrice`	No	Max price in GBP
`minPrice`	No	Min price in GBP
`furnished`	No	Only furnished listings
`propertyType`	No	Raw property type (apartment, villa, …) or K75 group slug: house (villa+detached+bungalow), land, commercial

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`offset`	Yes
`fxRates`	No
`ranking`	No
`factType`	No
`listings`	Yes
`dataSource`	No
`isEstimate`	No
`sortApplied`	Yes
`totalMatched`	Yes
`appliedFilters`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed24 schema fields changedv2.1.0Sep 14, 2026

changedInput schema / properties / city / description

Previous value: -"City to filter"New value: +"Slug, Turkish name, or exonym (Kyrenia/Nicosia/Famagusta/Morphou)."

removedInput schema / properties / city / enum

Removed value: -[
-  "girne",
-  "iskele",
-  "lefkosa",
-  "gazimagusa",
-  "guzelyurt",
-  "lefke"
-]

addedInput schema / properties / district

Added value: +{
+  "description": "District name (e.g. Alsancak), matched accent/case-insensitively against the active-listing district list",
+  "type": "string"
+}

addedInput schema / properties / elevator

Added value: +{
+  "description": "Only listings with an elevator",
+  "type": "boolean"
+}

addedInput schema / properties / furnished

Added value: +{
+  "description": "Only furnished listings",
+  "type": "boolean"
+}

addedInput schema / properties / garden

Added value: +{
+  "description": "Only listings with a garden",
+  "type": "boolean"
+}

addedInput schema / properties / offset

Added value: +{
+  "description": "Rows to skip (pagination, default 0)",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / parking

Added value: +{
+  "description": "Only listings with parking",
+  "type": "boolean"
+}

addedInput schema / properties / pool

Added value: +{
+  "description": "Only listings with a pool",
+  "type": "boolean"
+}

addedInput schema / properties / propertyType

Added value: +{
+  "description": "Raw property type (apartment, villa, …) or K75 group slug: house (villa+detached+bungalow), land, commercial",
+  "enum": [
+    "apartment",
+    "residence",
+    "villa",
+    "twin",
+    "detached",
+    "bungalow",
+    "penthouse",
+    "studio",
+    "duplex",
+    "shop",
+    "office",
+    "warehouse",
+    "whole_building",
+    "hotel",
+    "residential_land",
+    "commercial_land",
+    "farmland",
+    "house",
+    "land",
+    "commercial"
+  ],
+  "type": "string"
+}

addedInput schema / properties / seaView

Added value: +{
+  "description": "Only listings flagged sea_view",
+  "type": "boolean"
+}

addedInput schema / properties / sortBy

Added value: +{
+  "description": "Sort order (default: newest)",
+  "enum": [
+    "newest",
+    "price_asc",
+    "price_desc",
+    "area_desc",
+    "price_per_sqm_asc"
+  ],
+  "type": "string"
+}

changedInput schema / properties / type / enum

Previous value: -[
-  "sale",
-  "rent",
-  "daily"
-]New value: +[
+  "sale",
+  "rent"
+]

addedOutput schema / properties / appliedFilters

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "bedrooms": {
+      "type": "number"
+    },
+    "city": {
+      "type": "string"
+    },
+    "district": {
+      "type": "string"
+    },
+    "elevator": {
+      "type": "boolean"
+    },
+    "furnished": {
+      "type": "boolean"
+    },
+    "garden": {
+      "type": "boolean"
+    },
+    "maxPrice": {
+      "type": "number"
+    },
+    "minPrice": {
+      "type": "number"
+    },
+    "parking": {
+      "type": "boolean"
+    },
+    "pool": {
+      "type": "boolean"
+    },
+    "propertyType": {
+      "type": "string"
+    },
+    "seaView": {
+      "type": "boolean"
+    },
+    "type": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

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 / listings / items

Added value: +{
+  "properties": {
+    "areaSqm": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "bedrooms": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "city": {
+      "type": "string"
+    },
+    "coverImageUrl": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "currency": {
+      "type": "string"
+    },
+    "district": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "listingNumber": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "locationPrecision": {
+      "enum": [
+        "exact",
+        "district",
+        "city"
+      ],
+      "type": "string"
+    },
+    "monthlyRentGbp": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "price": {
+      "type": "number"
+    },
+    "priceGbp": {
+      "type": "number"
+    },
+    "propertyType": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "title": {
+      "type": "string"
+    },
+    "type": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "title",
+    "city",
+    "district",
+    "price",
+    "priceGbp",
+    "currency",
+    "type",
+    "url"
+  ],
+  "type": "object"
+}

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

addedOutput schema / properties / ranking

Added value: +{
+  "properties": {
+    "of": {
+      "type": "number"
+    },
+    "pooled": {
+      "type": "number"
+    },
+    "scope": {
+      "enum": [
+        "complete",
+        "partial"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "scope",
+    "pooled",
+    "of"
+  ],
+  "type": [
+    "object",
+    "null"
+  ]
+}

addedOutput schema / properties / sortApplied

Added value: +{
+  "enum": [
+    "newest",
+    "price_asc",
+    "price_desc",
+    "area_desc",
+    "price_per_sqm_asc"
+  ],
+  "type": "string"
+}

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

addedOutput schema / required

Added value: +[
+  "count",
+  "totalMatched",
+  "offset",
+  "sortApplied",
+  "listings",
+  "appliedFilters"
+]

First observedv1.6.0Jul 30, 2026

TDQS

A4.2/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 default ordering, that limit caps returned rows, that totalMatched reports the full match count, and explicitly states what the tool does NOT return (valuation, verification, forecast, ranking, recommendation). This is rich, non-contradictory context that meaningfully shapes agent expectations.

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?

Three compact sentences: the first states the action, the second explains ordering and count semantics, and the third lists explicit exclusions. No filler or repetition, and key facts are front-loaded.

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 16-parameter tool with 100% schema coverage and an output schema, the description covers all necessary operational context: purpose, default order, pagination semantics, and explicit disclaimers about result scope. An agent can select and invoke it correctly without needing additional details.

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%, so the schema documents all 16 parameters. The description adds value by defining 'limit' as capping rows, introducing 'totalMatched' as the full match count, and clarifying that the search targets sale and long-term-rent listing types. This goes slightly beyond the schema descriptions.

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 identifies a specific verb ('Search') and resource ('live active sale and long-term-rent listings on Evlek'), with the title adding 'Northern Cyprus Property Listings'. It does not explicitly contrast with sibling 'search', but the scope and platform-specific wording make the tool's purpose distinguishable.

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?

Implied usage is clear: use this tool to find active sale and long-term rent listings, with default newest-first ordering and pagination. However, it does not name any alternatives or state when to prefer get_listing_by_number, compare_cities, or search instead.

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

Deploy Server