Skip to main content
Glama

get_booking_link

Read-onlyIdempotent

Re-prices one stay for exact dates and guests and returns a ZMRM booking link that opens the stay with the same dates and guests pre-filled. The quote carries priced_at and valid_until (advisory, not a hold). Payment always happens in ZMRM checkout; this tool never books or charges.

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>",
      "check_in": "<check_in>",
      "check_out": "<check_out>",
      "adults": "<adults>"
    },
    "name": "get_booking_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe stay id (uuid) from search_stays or get_stay.
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.
adultsYesNumber 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_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.
check_outYesDeparture 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."
    • 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 id (uuid) from search_stays or get_stay."
    • 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.4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses that the returned quote carries priced_at and valid_until, that validity is advisory and not a hold, and that no booking or charge occurs. These are exactly the semantics an agent needs to avoid treating the returned price as a reservation.

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?

Three short sentences, front-loaded with what is produced, followed by the quote validity caveat and the payment boundary. No restatement of the name or schema and nothing redundant.

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 an 11-parameter, read-only link generator with a fully documented schema and no output schema, the description covers output meaning (pre-filled link plus quote with priced_at/valid_until) and the booking boundary. It does not mention failure or staleness behavior -- e.g., what happens if the stay is unavailable or the price changed materially on re-pricing -- which would round it out.

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%, with per-parameter documentation for id, dates, guest counts, currency, locale, nationality, pets, and agent, so the schema carries the parameter burden. The description adds only the aggregate notion of 'exact dates and guests' and does not elaborate on any individual field, which is the expected baseline here.

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 uses a specific verb pair ('Re-prices... returns') against a concrete resource (a ZMRM booking link for one stay) and states the exact scope it operates on: one stay, exact dates and guests. That distinguishes it from the retrieval siblings (search_stays, get_stay) whose outputs are listings/details rather than a link.

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 makes the use case clear -- converting an identified stay into a pre-filled, bookable link with a fresh price -- and explicitly rules out the wrong expectation by stating 'this tool never books or charges,' with payment deferred to ZMRM checkout. It stops short of naming an alternative or stating prerequisites (e.g., obtain the id from search_stays/get_stay first), so it is strong context without explicit when-not 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