Skip to main content
Glama
Evlek

Evlek — Northern Cyprus Property MCP Server

Official
by Evlek
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Currency Conversion (payment-plan name reserved)

payment_plan
Read-only

Convert a property asking price into GBP, EUR, USD, or TRY to compare Northern Cyprus listings. Note: a full payment-plan schedule is planned but not yet available.

Instructions

Currently returns currency conversion only. A real installment/payment-schedule tool is planned under this name; until then it does not produce a payment plan, deposit schedule, or acquisition-cost estimate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
priceYesEntered property asking-price amount; not a deposit or installment.
currencyNoCurrency of the price (default GBP).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
fxNo
amountsYes
priceGBPYes
dataSourceNo
inputCurrencyYes
usesStoredRateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv2.1.0
    • removedInput schema / properties / offPlan
      Removed value: -{
-  "description": "True if off-plan (under construction).",
-  "type": "boolean"
-}
    • changedInput schema / properties / price / description
      Previous value: -"Property price."New value: +"Entered property asking-price amount; not a deposit or installment."
    • addedOutput schema / properties / amounts / properties
      Added value: +{
+  "EUR": {
+    "type": "number"
+  },
+  "GBP": {
+    "type": "number"
+  },
+  "TRY": {
+    "type": "number"
+  },
+  "USD": {
+    "type": "number"
+  }
+}
    • addedOutput schema / properties / amounts / required
      Added value: +[
+  "GBP",
+  "EUR",
+  "USD",
+  "TRY"
+]
    • addedOutput schema / properties / dataSource
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / fx / properties
      Added value: +{
+  "asOf": {
+    "type": "string"
+  },
+  "base": {
+    "enum": [
+      "GBP"
+    ],
+    "type": "string"
+  },
+  "rates": {
+    "properties": {
+      "EUR": {
+        "type": "number"
+      },
+      "GBP": {
+        "type": "number"
+      },
+      "TRY": {
+        "type": "number"
+      },
+      "USD": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "GBP",
+      "EUR",
+      "USD",
+      "TRY"
+    ],
+    "type": "object"
+  },
+  "source": {
+    "enum": [
+      "stored_current_rates"
+    ],
+    "type": "string"
+  }
+}
    • addedOutput schema / properties / fx / required
      Added value: +[
+  "base",
+  "source",
+  "asOf",
+  "rates"
+]
    • removedOutput schema / properties / offPlan
      Removed value: -{
-  "type": "boolean"
-}
    • addedOutput schema / properties / usesStoredRate
      Added value: +{
+  "type": "boolean"
+}
    • removedOutput schema / properties / warnings
      Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
    • addedOutput schema / required
      Added value: +[
+  "inputCurrency",
+  "priceGBP",
+  "amounts"
+]
  2. First observedv1.6.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and non-destructive behavior. The description adds meaningful context by revealing that this is a temporary placeholder that only returns currency conversion, going beyond what the annotations convey and preventing false expectations about payment-plan outputs.

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 concise sentences. The first front-loads the actual current behavior, and the second prevents misuse by listing what the tool does not do and explaining the placeholder situation. Every sentence earns its place.

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?

For a simple two-parameter tool with an output schema and safety annotations, the description covers the essential caveat that the tool name is misleading. It could have pointed explicitly to convert_currency as the canonical sibling, but nothing critical is missing for correctly invoking a basic currency conversion.

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 baseline is 3. The description itself adds no parameter-specific detail; the schema already explains that price is the asking price and not a deposit or installment, and currency is the price currency.

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 the tool currently performs currency conversion only, and explicitly disclaims payment-plan, deposit, and acquisition-cost outputs. This distinguishes it from the misleading name, though it does not explicitly differentiate it from the sibling convert_currency.

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 the tool should be used for currency conversion and warns against using it for payment plans or related estimates. However, it never explicitly says when to prefer this tool over the sibling convert_currency, and it lacks clear when-to-use versus when-not-to-use guidance.

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

Deploy Server

Other Tools