Skip to main content
Glama

Home details

get_property
Read-onlyIdempotent

Full details for one property by property_key (from search results): description, amenities, photos, house rules, cancellation, recent reviews (no names), and — when dates are given — a price_breakdown (INSTANT) or an availability_note (ON_REQUEST). Always includes booking_link. 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).

LOYALTY BONUS: when a result includes loyalty_bonus, mention it. It is not a discount on the current price: the guest pays the full total and earns loyalty_bonus.amount € as credit for a future stay on HotelsCasa (1 € per night). Present it as credit for later, never as a reduction of this 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoLanguage of the answer: es, en, de, fr, it, pt, tr or ru. Default es.
guestsNo
check_inNoYYYY-MM-DD.
check_outNoYYYY-MM-DD.
property_keyYesThe property_key returned by search_properties.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNo
lngNo
cityNo
nameNo
typeNo
errorNo
roomsNo
photosNo
ratingNo
regionNo
countryNo
messageNo
reviewsNo
bedroomsNo
amenitiesNo
availableNo
bathroomsNo
max_guestsNo
price_fromNo
price_noteNo
descriptionNo
price_totalNo
short_pitchNo
booking_linkNo
booking_modeNo
cancellationNo
property_keyNo
property_typeNo
reviews_countNo
text_languageNo
thumbnail_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The description goes far beyond the annotations (readOnlyHint, idempotentHint, destructiveHint) by detailing the two property types, the obligation to present on_request as available, the golden booking_link rule, the loyalty bonus mechanics, price field semantics, and the need to translate text. It also includes negative instructions (e.g., never compute totals, never strip link parameters). This is rich, transparent behavior disclosure with no contradictions.

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?

The description is long but well-structured with clear headings (PRICE FIELDS, LOYALTY BONUS, GOLDEN LINK RULE, TEXT LANGUAGE) and front-loaded purpose. While some repetition exists (e.g., 'never describe them as unavailable' appears twice), every section conveys essential operational rules. It is arguably longer than ideal but remains organized and relevant.

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?

Given the tool's complexity, the description covers return content, pricing behavior, booking links, language handling, and edge cases (no dates, on_request). It explains the difference between indicative and confirmed prices, and it references an output schema. No critical operational detail is missing for an agent to correctly present property information.

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 80%, with descriptions for lang, check_in, check_out, and property_key; guests lacks a description. The description adds meaning by explaining that check_in/check_out enable price_breakdown or availability_note, and that without dates price_from is only indicative. It also clarifies property_key's origin. This adds value beyond the schema, though it doesn't elaborate on the guests parameter's purpose.

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 states a specific verb ('get') and resource ('property'), and clearly defines the output: full details for one property by property_key, including description, amenities, photos, house rules, cancellation, reviews, and pricing. It also distinguishes itself from search_properties (which returns search results) and check_availability (which is for availability checks), and it even addresses hotels within its scope. The purpose is unambiguous and differentiates well from siblings.

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?

The description provides clear usage context: it is to be used after search_properties, and it instructs to call check_availability when dates are needed. It also explains how to handle on_request vs instant properties. However, it does not explicitly mention when to use get_hotel instead of get_property, despite hotels being covered here; this leaves a small ambiguity in sibling differentiation.

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.