Evlek — Northern Cyprus Property MCP Server

Official

by Evlek

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

Get Northern Cyprus Price Index

get_price_index

Read-only

Retrieve source-dated asking-price indices for properties in Northern Cyprus, with optional city and sale/rent filters. Returns current listing averages, not transactions or valuations.

Instructions

Returns source-dated aggregates of live active Evlek sale or long-term-rent asking prices. Descriptive listing facts only: not completed transactions, a valuation, a forecast, or an investment recommendation.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`city`	No	Filter to a single city (omit for all cities). Slug, Turkish name, or exonym (Kyrenia/Nicosia/Famagusta/Morphou).
`type`	No	Sale or rent (default: sale)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`type`	Yes
`cities`	Yes
`dataAsOf`	Yes
`dataSource`	No
`isEstimate`	No
`metricType`	No
`totalListings`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv2.1.0Sep 14, 2026

addedInput schema / properties / city / description

Added value: +"Filter to a single city (omit for all cities). Slug, Turkish name, or exonym (Kyrenia/Nicosia/Famagusta/Morphou)."

removedInput schema / properties / city / enum

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

addedOutput schema / properties / cities / items

Added value: +{
+  "properties": {
+    "city": {
+      "type": "string"
+    },
+    "count": {
+      "type": "number"
+    },
+    "districts": {
+      "items": {
+        "properties": {
+          "count": {
+            "type": "number"
+          },
+          "district": {
+            "type": "string"
+          },
+          "lowSample": {
+            "type": "boolean"
+          },
+          "medianPrice": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "medianPricePerSqm": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "provenance": {
+            "properties": {
+              "agencies": {
+                "type": [
+                  "number",
+                  "null"
+                ]
+              },
+              "maxAgencyShare": {
+                "type": [
+                  "number",
+                  "null"
+                ]
+              },
+              "publishers": {
+                "type": [
+                  "number",
+                  "null"
+                ]
+              },
+              "singleSource": {
+                "type": "boolean"
+              }
+            },
+            "required": [
+              "publishers",
+              "agencies",
+              "maxAgencyShare",
+              "singleSource"
+            ],
+            "type": "object"
+          },
+          "status": {
+            "type": "string"
+          },
+          "withheldReason": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "district",
+          "count",
+          "lowSample",
+          "medianPrice"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "lowSample": {
+      "type": "boolean"
+    },
+    "medianPrice": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "medianPricePerSqm": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "p25Price": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "p75Price": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "provenance": {
+      "properties": {
+        "agencies": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "maxAgencyShare": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "publishers": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "singleSource": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "publishers",
+        "agencies",
+        "maxAgencyShare",
+        "singleSource"
+      ],
+      "type": "object"
+    },
+    "status": {
+      "enum": [
+        "proven",
+        "preliminary",
+        "collecting"
+      ],
+      "type": "string"
+    },
+    "withheldReason": {
+      "enum": [
+        "insufficient_sample",
+        "no_value",
+        null
+      ],
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "city",
+    "count",
+    "status",
+    "lowSample",
+    "withheldReason",
+    "medianPrice",
+    "districts"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / dataAsOf

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

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

removedOutput schema / properties / generatedAt

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

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

addedOutput schema / required

Added value: +[
+  "type",
+  "dataAsOf",
+  "cities"
+]

First observedv1.6.0Jul 30, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds meaningful context beyond that: data is 'source-dated', 'live active', and based on 'asking prices' only, and it clarifies that output is descriptive facts rather than investment advice. This helps the agent interpret results correctly.

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?

Two tight sentences with zero waste. The first states the action and key qualifiers; the second draws a clear boundary of what the data is not. Every phrase contributes to understanding.

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 lightweight read-only tool with two optional, fully documented parameters and an output schema, the description covers the essential semantics, scope, and limitations. An agent can safely invoke it and know what kind of output to expect without missing critical context.

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?

The input schema has 100% parameter description coverage, so the description does not need to compensate. It echoes the 'sale or rent' distinction from the type parameter but adds no meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 names a specific verb ('Returns'), a clear resource ('source-dated aggregates of live active Evlek sale or long-term-rent asking prices'), and explicitly scopes away from completed transactions, valuations, forecasts, and recommendations. This distinguishes it from sibling listing/search tools, which target individual properties or comparisons.

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 implies use for market-level asking-price analytics and explicitly lists exclusions ('not completed transactions, a valuation, a forecast, or an investment recommendation'). However, it does not explicitly name an alternative tool or state a direct routing condition such as 'use this for aggregates, use search for listings', so the guidance is more implied than explicit.

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

Deploy Server