Palmera Cyprus catalogue

Search new-build projects in Cyprus

search_projects

Read-only

Search the catalogue of new-build projects in Cyprus (the same projects the site shows). Filter by district, neighbourhood or zone, starting price in euros (before VAT), distance to the sea, construction status and kind of home. Returns matching projects with starting price, homes, status, distances and page path. Use it for any question about what is available where or for how much.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_projects"
  }
}

Input Schema

Name	Required	Description
`kind`	No
`sort`	No
`limit`	No	How many projects to return (default 6, max 12).
`place`	No	A neighbourhood or zone name or id, in Hebrew or English (e.g. 'גרמסוגיה', 'Kato Paphos', 'limassol-east', 'קורל ביי').
`status`	No
`district`	No	Catalogue district.
`max_sea_km`	No	Furthest distance to the sea in km (0.6 = walking distance).
`max_price_eur`	No	Highest starting price, euros before VAT.
`min_price_eur`	No	Lowest starting price, euros before VAT.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 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 openWorldHint: false, so the safety profile is clear. The description adds useful context about return fields (starting price, homes, status, distances, page path) and clarifies that prices are before VAT, which helps interpret results. It does not cover pagination or rate limits, but those are less critical given 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 four efficient sentences, front-loaded with the core action ('Search the catalogue...') and then covering filters, returns, and usage. Every sentence adds value without redundancy.

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?

Given 9 parameters and no output schema, the description adequately covers what the tool does, how to filter, what is returned, and when to use it. Minor gaps remain: the sort parameter's behavior and the default limit (6) are not mentioned, though the limit's default is specified in the schema.

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 67%, so some parameters (e.g., status, kind) lack schema descriptions. The description mentions filtering by district, neighbourhood, zone, price, distance, status, and kind, which adds meaning for status and kind, but it does not explain the sort parameter or its enum values. The price semantics are redundant with the schema, so overall the description provides only partial compensation for the coverage 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?

The description states a specific verb (Search) and resource (catalogue of new-build projects in Cyprus) with clear scope. It distinguishes from siblings by focusing on discovery ('what is available where') versus detail retrieval (get_project) and pricing (purchase_costs), though it doesn't name alternatives explicitly.

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 final sentence provides explicit usage context: 'Use it for any question about what is available where or for how much.' It does not state when not to use the tool or name alternatives like get_project, but the guidance is clear for typical queries.

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

All Palmera Cyprus catalogue 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.

Resources

Need Help?