Skip to main content
Glama

Check home availability

check_availability
Read-onlyIdempotent

Check availability and price for up to 10 properties on given dates. THIS is the tool that answers «is it free on my dates and what does it cost»: search_properties never does. Use the property_key from search_properties results, and call it as soon as the traveller gives dates — never search the web instead. For INSTANT objects returns available (true/false) and, when free, a price_breakdown. For ON_REQUEST objects returns available:null with a price_note and a booking_link to the enquiry form — this is NOT a failure, it is the normal path for most of the catalogue. Results include two kinds of properties. Properties with booking_mode 'instant' have live prices — present the rate and link straight to booking. Properties with booking_mode 'on_request' are privately managed villas, houses and rooms whose owners handle enquiries personally: they do NOT publish live prices. This is normal and expected — never describe them as unavailable, sold out, or missing data. Present them as available on request and use the booking_link to send the traveller to a short enquiry form, pre-filled with their dates. The owner replies personally.

Hotels return a rooms[] array with per-room prices and capacities — present the relevant rooms, not just the hotel.

When no dates are given, price_from is only an indicative minimum. Seasonal, weekend and holiday rates apply. Always ask the traveller for dates, then call check_availability. Prices are indicative and confirmed on the property page.

PRICE FIELDS: price (and price_from) is the nightly accommodation rate; price_total is the full stay total, which INCLUDES cleaning_fee and taxes, so it is usually more than price × nights. Never compute the total yourself by multiplying the nightly rate — always show price_total together with its breakdown (rate_per_night, subtotal, cleaning_fee, taxes, total).

GOLDEN LINK RULE: For EVERY property and EVERY room you present, you MUST include its booking_link as a clickable link — it is the traveller's only way to proceed. Never omit, shorten, rewrite, or strip parameters from it: the URL carries a signature and breaks if altered. Return it verbatim. Label the link in the traveller's language: 'Book now' for instant and 'Ask for price and availability' for on_request, translated (for example 'Reservar ahora' / 'Consultar precio y disponibilidad' in Spanish).

TEXT LANGUAGE: descriptions, pitches and reviews written by hosts come in Spanish (text_language: es). Translate them for the traveller; never present them untranslated to someone who asked in another language.

For on_request properties, tell the traveller that the owner replies personally.

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": {
      "items": "<items>"
    },
    "name": "check_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer: es, en, de, fr, it, pt, tr or ru. Default es.
itemsYes

Output Schema

NameRequiredDescriptionDefault
errorNo
localeNo
messageNo
resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the bar is lower, yet the description adds substantial behavior the annotations cannot carry: available:null for ON_REQUEST is 'NOT a failure', the two booking_modes and what each returns, hotels returning rooms[], and that price_total includes cleaning_fee and taxes so it must never be recomputed. It also discloses the signature-bearing booking_link integrity rule and host-language content, which are real operational constraints.

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

Conciseness3/5

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

The purpose is front-loaded in the first two sentences, which is right, but the instant/on_request distinction is made twice — once as a terse field list ('For INSTANT objects...') and again in the longer 'Results include two kinds of properties' paragraph. That duplication plus heavy ALL-CAPS emphasis inflates a long description without adding information; the price-field and link rules do earn their place.

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?

An output schema exists, so return structures need not be spelled out, yet the description still pre-empts the two most likely agent misreadings: treating available:null as unavailability, and multiplying nightly rate by nights instead of showing price_total with its breakdown. For a 2-param tool with a nested items array, nothing an agent needs to call and interpret it is missing.

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 description coverage is 50%, so some compensation is needed. The description reinforces property_key provenance ('from search_properties results') and the 10-item ceiling, and the TEXT LANGUAGE block gives real meaning to the lang parameter that the schema only lists as values. It says little explicit about guests or the check_in/check_out relationship (the schema already labels the date format), leaving a small 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 opening sentence gives a specific verb, resource, cardinality and scope: 'Check availability and price for up to 10 properties on given dates.' It then explicitly separates itself from the nearest sibling: 'THIS is the tool that answers «is it free on my dates and what does it cost»: search_properties never does.' An agent can route between check_availability and search_properties without opening either schema.

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?

When-to-use is stated with prerequisites and exclusions: consume property_key from search_properties results, call as soon as the traveller supplies dates, ask for dates when missing, and 'never search the web instead.' The one ambiguous case the agent might hit — no dates given — is also covered, with instructions to treat price_from as indicative only.

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.