Evlek — Northern Cyprus Property MCP Server

Search Northern Cyprus Property Listings

search_listings

Read-only

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)
`query`	No	Optional free-text query (parsed like the `search` tool); merges with explicit filters below — an explicit filter wins on conflict
`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
`notes`	No
`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.

Changed2 schema fields changedSep 10, 2026

addedInput schema / properties / query

Added value: +{
+  "description": "Optional free-text query (parsed like the `search` tool); merges with explicit filters below — an explicit filter wins on conflict",
+  "type": "string"
+}

addedOutput schema / properties / notes

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed7 schema fields changedSep 8, 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"
-]

changedInput schema / properties / district / description

Previous value: -"District name (e.g. Alsancak), case-insensitive"New value: +"District name (e.g. Alsancak), matched accent/case-insensitively against the active-listing district list"

addedOutput schema / properties / appliedFilters / additionalProperties
```
Added value: +false
```

addedOutput schema / properties / appliedFilters / properties

Added value: +{
+  "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"
+  }
+}

addedOutput schema / properties / fxRates / properties

Added value: +{
+  "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"
+    ]
+  }
+}

addedOutput schema / properties / fxRates / required

Added value: +[
+  "base",
+  "rates",
+  "source",
+  "updatedAt",
+  "isFallback"
+]

Changed15 schema fields changedSep 8, 2026

addedInput schema / properties / district

Added value: +{
+  "description": "District name (e.g. Alsancak), case-insensitive",
+  "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"
+}

changedInput schema / properties / propertyType / description

Previous value: -"Property type filter"New value: +"Raw property type (apartment, villa, …) or K75 group slug: house (villa+detached+bungalow), land, commercial"

changedInput schema / properties / propertyType / enum

Previous value: -[
-  "apartment",
-  "residence",
-  "villa",
-  "twin",
-  "detached",
-  "bungalow",
-  "penthouse",
-  "studio",
-  "duplex",
-  "shop",
-  "office",
-  "warehouse",
-  "whole_building",
-  "hotel",
-  "residential_land",
-  "commercial_land",
-  "farmland"
-]New value: +[
+  "apartment",
+  "residence",
+  "villa",
+  "twin",
+  "detached",
+  "bungalow",
+  "penthouse",
+  "studio",
+  "duplex",
+  "shop",
+  "office",
+  "warehouse",
+  "whole_building",
+  "hotel",
+  "residential_land",
+  "commercial_land",
+  "farmland",
+  "house",
+  "land",
+  "commercial"
+]

addedInput schema / properties / seaView

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

addedOutput schema / properties / fxRates

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

addedOutput schema / properties / listings / items / properties / monthlyRentGbp
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
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"
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "count",
-  "totalMatched",
-  "sortApplied",
-  "listings",
-  "appliedFilters"
-]New value: +[
+  "count",
+  "totalMatched",
+  "offset",
+  "sortApplied",
+  "listings",
+  "appliedFilters"
+]

Changed1 schema field changedSep 3, 2026
- addedOutput schema / properties / listings / items / properties / locationPrecision
```
Added value: +{
+  "enum": [
+    "exact",
+    "district",
+    "city"
+  ],
+  "type": "string"
+}
```

Changed1 schema field changedAug 25, 2026

changedInput schema / properties / propertyType / enum

Previous value: -[
-  "apartment",
-  "residence",
-  "villa",
-  "twin",
-  "detached",
-  "bungalow",
-  "penthouse",
-  "studio",
-  "duplex",
-  "shop",
-  "office",
-  "warehouse",
-  "whole_building",
-  "residential_land",
-  "commercial_land",
-  "farmland"
-]New value: +[
+  "apartment",
+  "residence",
+  "villa",
+  "twin",
+  "detached",
+  "bungalow",
+  "penthouse",
+  "studio",
+  "duplex",
+  "shop",
+  "office",
+  "warehouse",
+  "whole_building",
+  "hotel",
+  "residential_land",
+  "commercial_land",
+  "farmland"
+]

Changed5 schema fields changedAug 8, 2026

changedInput schema / properties / type / enum

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

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

removedOutput schema / properties / fxRates

Removed value: -{
-  "properties": {
-    "base": {
-      "type": "string"
-    },
-    "isFallback": {
-      "type": "boolean"
-    },
-    "rates": {
-      "type": "object"
-    },
-    "source": {
-      "type": "string"
-    },
-    "updatedAt": {
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}

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

Changed7 schema fields changedAug 4, 2026

addedInput schema / properties / propertyType

Added value: +{
+  "description": "Property type filter",
+  "enum": [
+    "apartment",
+    "residence",
+    "villa",
+    "twin",
+    "detached",
+    "bungalow",
+    "penthouse",
+    "studio",
+    "duplex",
+    "shop",
+    "office",
+    "warehouse",
+    "whole_building",
+    "residential_land",
+    "commercial_land",
+    "farmland"
+  ],
+  "type": "string"
+}

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"
+}

addedOutput schema / properties / listings / items / properties / propertyType
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

addedOutput schema / properties / listings / items / required

Added value: +[
+  "id",
+  "title",
+  "city",
+  "district",
+  "price",
+  "priceGbp",
+  "currency",
+  "type",
+  "url"
+]

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",
+  "sortApplied",
+  "listings",
+  "appliedFilters"
+]

Changed1 schema field changedAug 2, 2026

addedOutput schema / properties / fxRates

Added value: +{
+  "properties": {
+    "base": {
+      "type": "string"
+    },
+    "isFallback": {
+      "type": "boolean"
+    },
+    "rates": {
+      "type": "object"
+    },
+    "source": {
+      "type": "string"
+    },
+    "updatedAt": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedAug 1, 2026
- addedOutput schema / properties / appliedFilters
```
Added value: +{
+  "type": "object"
+}
```

Changed1 schema field changedAug 1, 2026

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"
+      ]
+    },
+    "price": {
+      "type": "number"
+    },
+    "priceGbp": {
+      "type": "number"
+    },
+    "title": {
+      "type": "string"
+    },
+    "type": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedJun 2, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "type": "number"
+    },
+    "listings": {
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Changed5 schema fields changedApr 23, 2026
- addedInput schema / properties / bedrooms / description
```
Added value: +"Bedroom count (integer 0-10)"
```
- changedInput schema / properties / bedrooms / type
```
Previous value: -"integer"New value: +"number"
```
- removedInput schema / properties / limit / default
```
Removed value: -5
```
- addedInput schema / properties / limit / description
```
Added value: +"Result count (integer 1-10, default 5)"
```
- changedInput schema / properties / limit / type
```
Previous value: -"integer"New value: +"number"
```
First observedApr 17, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The annotations already declare this read-only and non-destructive, so the description's job is lighter. It adds meaningful behavior beyond the annotations: newest-first default, `limit` truncation, `totalMatched` reporting, and the caveat that it is not a valuation, verification, forecast, ranking, or recommendation tool. This gives the agent a clear, honest model of what the tool will and will not do.

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 three tightly focused sentences. It leads with the core purpose, then adds operational details (sorting, `limit`, `totalMatched`), and closes with a decisive scope boundary. There is no fluff or repetition.

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?

Given the tool's complexity (17 parameters), the description plus the fully populated schema and output presence covers nearly everything the agent needs: live scope, listings type, defaults, pagination reporting, and clear negative scope. The main remaining gap is the explicit comparison with sibling tools such as `search` and `compare_properties`; otherwise this definition is functionally complete.

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

Parameters3/5

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

Schema description coverage is 100%, and the schema already documents all 17 parameters well, with enums and per-field descriptions. The description adds minimal parameter-level depth; its only parameter-adjacent contributions are global behavior such as 'newest-first by default' and `totalMatched` semantics, which are useful but not substantial per-parameter enrichments.

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 a specific verb and resource: 'Search live active sale and long-term-rent listings on Evlek.' It differentiates by scope—only live active listings and only asking-price facts, not valuation or recommendations—but does not explicitly distinguish itself from the sibling `search` tool, leaving some room for confusion.

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 gives useful exclusionary guidance: it is for live active listings and returns only advertised asking-price facts, not valuation, forecast, ranking, or recommendation. However, it does not explicitly tell the agent when to prefer `search_listings` over siblings like `search`, `compare_properties`, or `get_listing_detail`, so alternative selection is left mostly to inference.

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

All Evlek — Northern Cyprus Property MCP Server tools Inspect

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.