Skip to main content
Glama
Evlek

Evlek — Northern Cyprus Property MCP Server

Official
by Evlek
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Fetch full Evlek listing detail

fetch
Read-only

Get full Evlek property details by listing ID from search: title, description, GBP price, location, size, amenities.

Instructions

Fetch the full detail of one Evlek listing by id (from search): title, description, GBP-normalized price, location, size, amenities. Same data as get_listing_detail — this fixed id-only form exists for the ChatGPT/OpenAI connector contract. Use when: an id from search is known. Don't use for: discovery — use search first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesEvlek listing id (UUID) from search

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
urlYes
textYes
titleYes
photosNo
metadataNo
coverImageUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.1.0
    • addedOutput schema / properties / coverImageUrl
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / metadata / properties
      Added value: +{
+  "areaSqm": {
+    "type": [
+      "number",
+      "null"
+    ]
+  },
+  "bedrooms": {
+    "type": [
+      "number",
+      "null"
+    ]
+  },
+  "city": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "currency": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "district": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "listedAt": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "locationPrecision": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "monthlyRentGbp": {
+    "type": [
+      "number",
+      "null"
+    ]
+  },
+  "priceGBP": {
+    "type": [
+      "number",
+      "null"
+    ]
+  },
+  "pricePerSqmGBP": {
+    "type": [
+      "number",
+      "null"
+    ]
+  },
+  "type": {
+    "type": [
+      "string",
+      "null"
+    ]
+  }
+}
    • addedOutput schema / properties / metadata / required
      Added value: +[
+  "city",
+  "district",
+  "type",
+  "bedrooms",
+  "areaSqm",
+  "priceGBP",
+  "pricePerSqmGBP",
+  "monthlyRentGbp",
+  "currency",
+  "listedAt",
+  "locationPrecision"
+]
    • addedOutput schema / properties / photos
      Added value: +{
+  "items": {
+    "properties": {
+      "caption": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "tags": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / required
      Added value: +[
+  "id",
+  "title",
+  "text",
+  "url"
+]
  2. First observedv1.6.0

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 useful behavioral context: it is id-only, returns GBP-normalized price, and mirrors get_listing_detail's data. No contradiction with 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 well-structured and front-loaded: it opens with the action and resource, then narrows to contract context and explicit usage rules. Every sentence contributes useful information without unnecessary 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?

For a one-parameter read-only tool with a rich output schema and annotations already present, the description covers what the tool does, what data it returns, when to use it, and when not to. Nothing critical is missing for correct invocation.

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 schema has 100% coverage for its single required parameter, including the UUID-from-search meaning. The description reinforces 'by id (from search)' but adds no meaning beyond the schema, so the baseline score of 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?

The description states a specific verb and resource: 'Fetch the full detail of one Evlek listing by id', and enumerates the exact data fields returned. It also distinguishes this tool from get_listing_detail by explaining it is the fixed id-only connector-contract form.

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?

It explicitly gives a use condition ('Use when: an id from search is known'), a don't-use condition ('Don't use for: discovery'), and names the alternative ('use search first'). However, because get_listing_detail is described as returning the same data, the description doesn't fully clarify when to choose fetch over get_listing_detail for non-connector use.

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