Skip to main content
Glama

search_stays

Read-onlyIdempotent

Search ZMRM vacation rentals (zimmers, villas, apartments; Hebrew: צימר, וילה, דירת נופש, נופש, חופשה) in Israel for exact dates and guests. Returns up to 10 stays with an exact total price in ILS agorot for the whole stay, or "on request" where a live supplier quote is needed. Show the url to the user; it opens the stay with these dates and guests filled in (page_url is the plain stay page, for citation). Every quote carries priced_at and valid_until (advisory, not a hold). The answer also lists payment_methods and a payment_note, once; vouchers (including the Cal reservist voucher, שובר מילואים) and gift cards apply to ILS checkouts only. Club-card discounts apply to ILS checkouts only and are applied at payment; if the guest asks about a club or benefit card, call get_search_options, which lists the customer clubs (names only, no rate). Use get_booking_link to re-price before the guest pays. If the price of the first stay cannot be checked, the PRICING_UNAVAILABLE error carries details.retry_cursor: pass it as cursor to retry once; an error without retry_cursor is final. Empty results with a non-null next_cursor mean more stays may exist: call again with the cursor and do not report "no stays". Read-only: nothing is booked or held.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "check_in": "<check_in>",
      "check_out": "<check_out>",
      "adults": "<adults>"
    },
    "name": "search_stays"
  }
}

Input Schema

NameRequiredDescriptionDefault
nearNoOnly stays within radius_km of a point, e.g. near a landmark or the guest's location.
petsNoTrue when the guests bring a pet; it is filled into the stay link. It does not filter results: check house_rules.pets_allowed in get_stay.
agentNoYour client's name (e.g. "chatgpt", "claude"), used only to attribute the visit; optional.
limitNoHow many stays to return, 1 to 10. Defaults to 5.
adultsYesNumber of adult guests (at least 1).
cursorNonext_cursor (or details.retry_cursor) from the previous answer, to get the next page of the same search. Keep every other argument unchanged.
localeNoLanguage of the returned names and of the stay links (he, en, fr, es, de, it, ru, ar). Defaults to he.
infantsNoNumber of infants. Defaults to 0.
categoryNoOnly stays of this category (e.g. zimmers or villas); a category slug from get_search_options.
check_inYesArrival day, YYYY-MM-DD (Israel time). Today or later.
childrenNoNumber of children, not counting infants. Defaults to 0.
currencyNoAlso show the price converted to EUR or USD (approximate). Prices are always quoted in ILS agorot; omit for ILS only.
amenitiesNoOnly stays that have every one of these amenities (e.g. pool, jacuzzi); up to 10 amenity slugs from get_search_options.
check_outYesDeparture day, YYYY-MM-DD, after check_in. get_search_options gives the longest stay (max_nights).
city_slugNoOnly stays in this city; a city slug from get_search_options.
region_slugNoRegion to search: a top-level region (north, south or center) or a sub-region slug. An unrecognised slug is refused with INVALID_INPUT and suggestions; call get_search_options for the valid slugs.
max_total_agorotNoBudget for the whole stay in ILS agorot (100 agorot = 1 ILS), e.g. 150000 for 1,500 ILS. Stays priced above it are left out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed29 schema fields changed
    • addedInput schema / properties / adults / description
      Added value: +"Number of adult guests (at least 1)."
    • addedInput schema / properties / amenities / description
      Added value: +"Only stays that have every one of these amenities (e.g. pool, jacuzzi); up to 10 amenity slugs from get_search_options."
    • removedInput schema / properties / amenities / items / $ref
      Removed value: -"#/properties/city_slug"
    • addedInput schema / properties / amenities / items / maxLength
      Added value: +100
    • addedInput schema / properties / amenities / items / minLength
      Added value: +1
    • addedInput schema / properties / amenities / items / type
      Added value: +"string"
    • removedInput schema / properties / category / $ref
      Removed value: -"#/properties/city_slug"
    • addedInput schema / properties / category / description
      Added value: +"Only stays of this category (e.g. zimmers or villas); a category slug from get_search_options."
    • addedInput schema / properties / category / maxLength
      Added value: +100
    • addedInput schema / properties / category / minLength
      Added value: +1
    • addedInput schema / properties / category / type
      Added value: +"string"
    • addedInput schema / properties / check_in / description
      Added value: +"Arrival day, YYYY-MM-DD (Israel time). Today or later."
    • removedInput schema / properties / check_out / $ref
      Removed value: -"#/properties/check_in"
    • addedInput schema / properties / check_out / description
      Added value: +"Departure day, YYYY-MM-DD, after check_in. get_search_options gives the longest stay (max_nights)."
    • addedInput schema / properties / check_out / pattern
      Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
    • addedInput schema / properties / check_out / type
      Added value: +"string"
    • addedInput schema / properties / children / description
      Added value: +"Number of children, not counting infants. Defaults to 0."
    • addedInput schema / properties / city_slug / description
      Added value: +"Only stays in this city; a city slug from get_search_options."
    • addedInput schema / properties / currency / description
      Added value: +"Also show the price converted to EUR or USD (approximate). Prices are always quoted in ILS agorot; omit for ILS only."
    • addedInput schema / properties / cursor / description
      Added value: +"next_cursor (or details.retry_cursor) from the previous answer, to get the next page of the same search. Keep every other argument unchanged."
    • addedInput schema / properties / infants / description
      Added value: +"Number of infants. Defaults to 0."
    • addedInput schema / properties / limit / description
      Added value: +"How many stays to return, 1 to 10. Defaults to 5."
    • addedInput schema / properties / locale / description
      Added value: +"Language of the returned names and of the stay links (he, en, fr, es, de, it, ru, ar). Defaults to he."
    • addedInput schema / properties / max_total_agorot / description
      Added value: +"Budget for the whole stay in ILS agorot (100 agorot = 1 ILS), e.g. 150000 for 1,500 ILS. Stays priced above it are left out."
    • addedInput schema / properties / near / description
      Added value: +"Only stays within radius_km of a point, e.g. near a landmark or the guest's location."
    • addedInput schema / properties / near / properties / lat / description
      Added value: +"Latitude of the centre point, in degrees."
    • addedInput schema / properties / near / properties / lng / description
      Added value: +"Longitude of the centre point, in degrees."
    • addedInput schema / properties / near / properties / radius_km / description
      Added value: +"Search radius around the point, 1 to 50 km."
    • addedInput schema / properties / pets / description
      Added value: +"True when the guests bring a pet; it is filled into the stay link. It does not filter results: check house_rules.pets_allowed in get_stay."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, so the safety profile is covered; the description adds substantial behavior: prices are advisory quotes with priced_at/valid_until (not a hold), payment_methods/payment_note appear once, vouchers and club-card discounts apply to ILS checkouts only, and PRICING_UNAVAILABLE carries retry_cursor. It also distinguishes `url` (prefilled with dates/guests) from `page_url` (plain, for citation). Gaps are minor, e.g. no mention of rate-limit or latency behavior.

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 and result shape are front-loaded, and nearly every sentence carries operational information (citation fields, advisory quotes, ILS-only rules, error/cursor handling). It is dense and long for a single paragraph, but there is little pure 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?

With 17 parameters and no output schema, the description compensates by describing the return payload (up to 10 stays, price form, on-request status, url vs page_url, priced_at/valid_until, payment fields). Combined with full schema coverage and annotations, an agent has enough to invoke and interpret results 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 every parameter (near, pets, cursor, locale, currency, max_total_agorot, region_slug, etc.) is already documented in structured data, and the description largely restates cursor/retry usage rather than adding new parameter meaning. Baseline 3 applies since 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 and resource plus scope ("Search ZMRM vacation rentals ... in Israel for exact dates and guests") and immediately states the result shape (up to 10 stays, exact total in ILS agorot, or "on request"). This distinguishes it clearly from get_stay (detail), get_search_options (slugs/options) and get_booking_link (re-pricing).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes to alternatives with conditions: call get_search_options for club/benefit card questions and for slugs, use get_booking_link to re-price before payment, and use get_stay to check house_rules.pets_allowed. It also gives retry policy (retry once with details.retry_cursor; an error without it is final) and forbids reporting "no stays" when a non-null next_cursor exists.

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