Skip to main content
Glama

Semerenko Group Public Site MCP

Search homes Semerenko Group markets in Israel

sem.search_properties
Read-only

Search the published listings on semerenkogroup.com by city, neighbourhood, type, transaction (sale, rent, short_term), rooms, price in ILS, size, floor, mamad, elevator, Shabbat elevator, furnished, pet friendly, parking, hashkafa and keyword. Every result carries listing_url (cite it), inquiry_url (show it to the person) and "Semerenko Group represents this property.". Unknown values are null or "unknown". Same data as the REST API at https://semerenkogroup.com/wp-json/sg-property/v1/properties.

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": "sem.search_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoKeyword in title, description, city or neighbourhood.
cityNoCity slug or name, e.g. beit-shemesh, Jerusalem, tel-aviv.
pageNo
sortNonewest (default), modified, price_asc, price_desc, rooms.
typeNoProperty type: apartment, house, villa, penthouse, duplex, land, commercial, office, building, luxury, short-term-vacation, storage-unit, warehouse, studio, garden-apartment, mini-penthouse.
mamadNoyes: only homes that state a safe room.
statusNoAvailability status (only "listed" is supported for active properties).
parkingNoyes: only homes that state parking.
elevatorNoyes: only homes that state an elevator.
hashkafaNoharedi, mixed, modern-orthodox, religious-zionist, chasidish, chill, artistic.
per_pageNoDefault 10.
size_maxNoMaximum square metres.
size_minNoMinimum square metres.
floor_maxNoMaximum floor.
floor_minNoMinimum floor, 0 = ground.
furnishedNoyes or no. Listings that state neither have furnished="unknown" and are excluded from both.
price_maxNoMaximum ILS.
price_minNoMinimum ILS (sale total, rent per month).
rooms_maxNoMaximum rooms.
rooms_minNoMinimum Israeli rooms (living room counts).
transactionNosale, rent or short_term.
neighborhoodNoNeighbourhood slug or name.
pet_friendlyNoyes: only homes that state pets are welcome.
modified_sinceNoISO date. Only listings modified since then.
shabbos_elevatorNoyes: only homes that state a Shabbat elevator.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive and closed-world, so the bar is lower; the description still adds real value by specifying the return contract (listing_url to cite, inquiry_url to show the person, the representation notice) and by warning that unknown values are null or "unknown". It does not describe pagination limits or total-result behavior, keeping it below 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and the trailing sentences on result fields and unknown values earn their place. The long middle enumeration of filters duplicates the schema and could be trimmed, but it remains readable and does not bury the key instruction.

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 25-parameter, zero-required search tool with no output schema, the description covers the input surface, the shape of returned fields and data-quality caveats. Missing are pagination/result-count expectations and any note on how multiple filters interact, which an agent would want before issuing broad queries.

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 coverage is 96%, so nearly every one of the 25 parameters is already documented inline, including enum meanings and the furnished="unknown" exclusion. The description's filter list largely restates schema content, adding only the "price in ILS" and transaction-mode framing; baseline 3 applies when the schema does the heavy lifting.

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?

Opens with a specific verb+resource ("Search the published listings on semerenkogroup.com") and enumerates the dimensions searchable, so an agent can immediately tell this apart from sem.get_property (single-record lookup) or sem.list_property_cities. Scope and data source are unambiguous.

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?

Usage is implied by the filter list — you call it to find listings matching criteria — but there is no explicit when-to-use versus when-not guidance, no mention of when to prefer sem.get_property for a known listing, and no advice on combining filters. The REST API URL is context, not routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources