Evlek — Northern Cyprus Property MCP Server

Compare Northern Cyprus Cities Side-by-Side

compare_cities

Read-only

Compare source-dated live active-listing asking-price aggregates across 2-4 Northern Cyprus cities. Descriptive listing facts only; not transaction prices, valuation, forecast, ranking, or investment advice.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`type`	No	Sale or rent (default: sale)
`cities`	Yes	Cities to compare (2-4)

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 8, 2026

addedInput schema / properties / cities / items / description

Added value: +"Slug, Turkish name, or exonym (Kyrenia/Nicosia/Famagusta/Morphou)."

removedInput schema / properties / cities / items / enum

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

addedOutput schema / properties / cities / items / properties / provenance / properties

Added value: +{
+  "agencies": {
+    "type": [
+      "number",
+      "null"
+    ]
+  },
+  "maxAgencyShare": {
+    "type": [
+      "number",
+      "null"
+    ]
+  },
+  "publishers": {
+    "type": [
+      "number",
+      "null"
+    ]
+  },
+  "singleSource": {
+    "type": "boolean"
+  }
+}

addedOutput schema / properties / cities / items / properties / provenance / required

Added value: +[
+  "publishers",
+  "agencies",
+  "maxAgencyShare",
+  "singleSource"
+]

Changed4 schema fields changedSep 8, 2026

addedOutput schema / properties / cities / items

Added value: +{
+  "properties": {
+    "activeCount": {
+      "type": "number"
+    },
+    "city": {
+      "type": "string"
+    },
+    "hasData": {
+      "type": "boolean"
+    },
+    "lowSample": {
+      "type": "boolean"
+    },
+    "medianPrice": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "medianPricePerSqm": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "p25Price": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "p75Price": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "provenance": {
+      "type": "object"
+    },
+    "slug": {
+      "type": "string"
+    },
+    "topDistrict": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "topDistrictMedianPrice": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "withheldReason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "slug",
+    "city",
+    "activeCount",
+    "hasData"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / dataAsOf

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

removedOutput schema / properties / generatedAt
```
Removed value: -{
-  "type": "string"
-}
```

changedOutput schema / required

Previous value: -[
-  "type",
-  "cities"
-]New value: +[
+  "type",
+  "dataAsOf",
+  "cities"
+]

Changed3 schema fields changedAug 8, 2026
- addedOutput schema / properties / dataSource
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / isEstimate
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / metricType
```
Added value: +{
+  "type": "string"
+}
```
Changed1 schema field changedAug 4, 2026
- addedOutput schema / required
```
Added value: +[
+  "type",
+  "cities"
+]
```

Changed1 schema field changedJun 2, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "cities": {
+      "type": "array"
+    },
+    "generatedAt": {
+      "type": "string"
+    },
+    "type": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedMay 31, 2026

changedInput schema / properties / cities / items / enum

Previous value: -[
-  "girne",
-  "iskele",
-  "lefkosa",
-  "gazimagusa"
-]New value: +[
+  "girne",
+  "iskele",
+  "lefkosa",
+  "gazimagusa",
+  "guzelyurt",
+  "lefke"
+]

Changed5 schema fields changedApr 23, 2026
- addedInput schema / properties / cities / description
```
Added value: +"Cities to compare (2-4)"
```
- removedInput schema / properties / cities / maxItems
```
Removed value: -4
```
- removedInput schema / properties / cities / minItems
```
Removed value: -2
```
- removedInput schema / properties / type / default
```
Removed value: -"sale"
```
- addedInput schema / properties / type / description
```
Added value: +"Sale or rent (default: sale)"
```
First observedApr 17, 2026

TDQS

A4.3/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 covered. The description adds meaningful behavioral context by specifying that it returns source-dated live active-listing asking-price aggregates and descriptive listing facts only, which clarifies the nature and limitations of the data beyond the annotations.

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 a single, tightly written sentence that front-loads the action and resource, then adds the important exclusions. Every element earns its place; there is no redundancy or filler.

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?

With annotations covering the read-only/destructive profile, a fully described input schema, an output schema present, and a description that states scope, data type, and exclusions, the description is complete for an agent to correctly select and invoke this tool. Return format is not needed because an output schema exists.

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%, so the input schema already documents both parameters. The description reinforces the 2-4 city constraint and the sale/rent context, but it does not add substantial meaning beyond what the schema already provides. Baseline 3 is appropriate here.

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 states a clear verb ('Compare') and a specific resource ('source-dated live active-listing asking-price aggregates across 2-4 Northern Cyprus cities'). It also distinguishes itself from valuation, forecast, and investment tools by explicitly excluding those categories, making it easy for an agent to identify what this tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use the tool: comparing city-level asking-price aggregates for 2-4 Northern Cyprus cities, for sale or rent. It also gives exclusions (not transaction prices, valuation, forecast, ranking, or investment advice). However, it does not explicitly name alternative sibling tools such as compare_properties or get_price_index, so the when-not-to-use guidance is present but not fully explicit.

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.