Skip to main content
Glama

get_stay

Read-onlyIdempotent

Get the public details of one ZMRM stay: description, amenities, house rules, check-in and check-out times, cancellation policy summary, images and location (approximate, rounded to about 1 km). With complete dates and guests it also returns a full price quote with the nightly breakdown, stamped with priced_at and valid_until (advisory, not a hold). Show the url to the user (it opens the stay, with these dates and guests filled in when you gave them); cite page_url, the plain stay page. 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). Read-only.

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": {
      "id": "<id>"
    },
    "name": "get_stay"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe stay: its id (uuid) from search_stays, or its ZMRM page path such as /zimmer/<category>/<region>/<city>/<slug>.
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.
adultsNoNumber of adult guests (at least 1).
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.
check_inNoArrival day, YYYY-MM-DD (Israel time). Today or later. Give dates and adults to get a price quote.
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.
check_outNoDeparture day, YYYY-MM-DD, after check_in. get_search_options gives the longest stay (max_nights).
nationalityNoLead guest's nationality, ISO 3166-1 alpha-2 in capitals (e.g. "IL", "US"). Some hotel rates depend on it. Defaults to IL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changed
    • addedInput schema / properties / adults / description
      Added value: +"Number of adult guests (at least 1)."
    • addedInput schema / properties / check_in / description
      Added value: +"Arrival day, YYYY-MM-DD (Israel time). Today or later. Give dates and adults to get a price quote."
    • 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 / 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 / id / description
      Added value: +"The stay: its id (uuid) from search_stays, or its ZMRM page path such as /zimmer/<category>/<region>/<city>/<slug>."
    • addedInput schema / properties / infants / description
      Added value: +"Number of infants. Defaults to 0."
    • 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 / nationality / description
      Added value: +"Lead guest's nationality, ISO 3166-1 alpha-2 in capitals (e.g. \"IL\", \"US\"). Some hotel rates depend on it. Defaults to IL."
    • 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.6/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, it discloses non-obvious behavior: location is rounded to about 1 km, the quote carries priced_at and valid_until and is advisory rather than a hold, vouchers and gift cards apply to ILS checkouts only, club discounts are applied at payment, and currency conversion is approximate. These are exactly the traits an agent cannot infer from structured fields.

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 field list are front-loaded, and most sentences carry distinct operational facts. The payment/voucher/club-card passage is dense and slightly over-packed for one paragraph, but no sentence is truly redundant.

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 11 parameters and no output schema, the description compensates by naming the key return fields (url, page_url, payment_methods, payment_note, priced_at, valid_until) and their caveats. An agent has everything needed to call it and interpret the result without guessing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real semantics: dates plus guests trigger the price quote, currency only adds a converted display while prices stay in ILS agorot, and the pets flag is carried into the stay link without filtering results. It adds value on top of an already well-documented schema.

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?

States a specific verb and resource ("Get the public details of one ZMRM stay") and enumerates exactly what comes back: description, amenities, house rules, times, cancellation summary, images, approximate location. It also separates itself from siblings by name, routing club/benefit-card questions to get_search_options.

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?

Clear context: use it for one known stay, pass complete dates and guests to get a price quote, and call get_search_options when the guest raises a club or benefit card. It never explicitly contrasts with search_stays or get_booking_link, so the when-not guidance is partial rather than complete.

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