Evlek — Northern Cyprus Property MCP Server

Get Live Asking-Price Context for a Northern Cyprus District

get_district_profile

Read-only

Returns source-dated active sale/long-term-rent listing counts and asking-price aggregates for one district. Any rent-to-price percentage is a derived asking-price ratio, not observed income, net yield, valuation, forecast, ranking, or recommendation.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`city`	Yes	City containing the district. Slug, Turkish name, or exonym (Kyrenia/Nicosia/Famagusta/Morphou).
`district`	Yes	District name (2-60 chars), matched accent/case-insensitively against the active-listing district list

Output Schema

TableJSON Schema

Name	Required	Description
`city`	Yes
`rent`	No
`sale`	No
`dataAsOf`	No
`district`	Yes
`truncated`	No
`dataSource`	No
`metricType`	No
`personaContexts`	No
`ratioMetricType`	No
`cleanSampleTotal`	Yes	sale.count + rent.count — clean sample size (IQR outliers excluded), not raw active listings
`isObservedIncome`	No
`askingRentToAskingPricePct`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedSep 8, 2026

addedInput schema / properties / city / description

Added value: +"City containing the district. 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 (2-60 chars)"New value: +"District name (2-60 chars), matched accent/case-insensitively against the active-listing district list"

addedOutput schema / properties / askingRentToAskingPricePct

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

removedOutput schema / properties / indicativeGrossRentToPricePct

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

addedOutput schema / properties / isObservedIncome
```
Added value: +{
+  "type": "boolean"
+}
```
removedOutput schema / properties / isObservedYield
```
Removed value: -{
-  "type": "boolean"
-}
```
addedOutput schema / properties / ratioMetricType
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / rent / properties / provenance / properties

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

addedOutput schema / properties / rent / properties / provenance / required

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

addedOutput schema / properties / sale / properties / provenance / properties

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

addedOutput schema / properties / sale / properties / provenance / required

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

addedOutput schema / properties / truncated
```
Added value: +{
+  "type": "boolean"
+}
```
removedOutput schema / properties / yieldMetricType
```
Removed value: -{
-  "type": "string"
-}
```

Changed6 schema fields changedSep 8, 2026

addedOutput schema / properties / cleanSampleTotal

Added value: +{
+  "description": "sale.count + rent.count — clean sample size (IQR outliers excluded), not raw active listings",
+  "type": "number"
+}

addedOutput schema / properties / dataAsOf

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

addedOutput schema / properties / rent / properties

Added value: +{
+  "count": {
+    "type": "number"
+  },
+  "maturity": {
+    "enum": [
+      "olgun",
+      "öncü",
+      "biriktiriyor"
+    ],
+    "type": "string"
+  },
+  "median": {
+    "type": [
+      "number",
+      "null"
+    ]
+  },
+  "medianPerSqm": {
+    "type": [
+      "number",
+      "null"
+    ]
+  },
+  "p25": {
+    "type": [
+      "number",
+      "null"
+    ]
+  },
+  "p75": {
+    "type": [
+      "number",
+      "null"
+    ]
+  },
+  "provenance": {
+    "type": "object"
+  },
+  "status": {
+    "enum": [
+      "proven",
+      "preliminary",
+      "collecting"
+    ],
+    "type": "string"
+  },
+  "withheldReason": {
+    "enum": [
+      "insufficient_sample",
+      "no_value",
+      null
+    ],
+    "type": [
+      "string",
+      "null"
+    ]
+  }
+}

addedOutput schema / properties / sale / properties

Added value: +{
+  "count": {
+    "type": "number"
+  },
+  "maturity": {
+    "enum": [
+      "olgun",
+      "öncü",
+      "biriktiriyor"
+    ],
+    "type": "string"
+  },
+  "median": {
+    "type": [
+      "number",
+      "null"
+    ]
+  },
+  "medianPerSqm": {
+    "type": [
+      "number",
+      "null"
+    ]
+  },
+  "p25": {
+    "type": [
+      "number",
+      "null"
+    ]
+  },
+  "p75": {
+    "type": [
+      "number",
+      "null"
+    ]
+  },
+  "provenance": {
+    "type": "object"
+  },
+  "status": {
+    "enum": [
+      "proven",
+      "preliminary",
+      "collecting"
+    ],
+    "type": "string"
+  },
+  "withheldReason": {
+    "enum": [
+      "insufficient_sample",
+      "no_value",
+      null
+    ],
+    "type": [
+      "string",
+      "null"
+    ]
+  }
+}

removedOutput schema / properties / totalActive
```
Removed value: -{
-  "type": "number"
-}
```

changedOutput schema / required

Previous value: -[
-  "city",
-  "district",
-  "totalActive"
-]New value: +[
+  "city",
+  "district",
+  "cleanSampleTotal"
+]

Changed8 schema fields changedAug 8, 2026

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

removedOutput schema / properties / grossYieldPct

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

addedOutput schema / properties / indicativeGrossRentToPricePct

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

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

addedOutput schema / properties / personaContexts

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

removedOutput schema / properties / personas

Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

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

Changed1 schema field changedAug 4, 2026
- addedOutput schema / required
```
Added value: +[
+  "city",
+  "district",
+  "totalActive"
+]
```

Changed1 schema field changedJun 2, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "city": {
+      "type": "string"
+    },
+    "district": {
+      "type": "string"
+    },
+    "grossYieldPct": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "personas": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "rent": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "sale": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "totalActive": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

Changed3 schema fields changedApr 23, 2026
- addedInput schema / properties / district / description
```
Added value: +"District name (2-60 chars)"
```
- removedInput schema / properties / district / maxLength
```
Removed value: -60
```
- removedInput schema / properties / district / minLength
```
Removed value: -2
```
AddedApr 17, 2026

TDQS

A4.2/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. The description adds valuable behavioral context: data is source-dated, reflecting active listings, and any rent-to-price percentage is a derived ratio rather than observed income, yield, valuation, forecast, ranking, or recommendation. This prevents misinterpretation of results.

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 two sentences with no filler. The first sentence front-loads the core behavior, and the second sentence adds an essential caveat about how rent-to-price percentages should be interpreted.

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?

With full schema coverage, annotations, and an output schema, the description is nearly complete. It adds the right disclaimers and scope. A small gap is the absence of any explicit pointer to sibling tools for multi-district comparisons, though this is not required for invoking the tool correctly.

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 both city and district parameters are fully documented there. The description adds no parameter-specific details beyond the single-district scope, so it does not need to compensate for any schema gap.

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 states a specific verb and resource: 'Returns source-dated active sale/long-term-rent listing counts and asking-price aggregates for one district.' It clearly identifies a single-district profile tool and distinguishes it from siblings like compare_cities or get_price_index.

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 gives clear context: use this tool when you need asking-price and listing-count aggregates for one district. It does not explicitly name alternatives or exclusions, but the single-district scope and output type make the intended usage reasonably obvious.

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.