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).

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": {
      "property_key": "<property_key>"
    },
    "name": "get_property"
  }
}

Input 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

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
Behavior4/5

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

Annotations already cover read-only/safe profile, but the description adds substantial behavioural context beyond them: the two booking_mode paths, the warning never to call on_request properties unavailable or sold out, the signed booking_link that breaks if altered, and Spanish host text needing translation. Only minor gap is nothing about response size or failure modes when property_key is invalid.

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?

Front-loaded with the purpose in the first clause, then clearly sectioned by PRICE FIELDS, GOLDEN LINK RULE and TEXT LANGUAGE. It is long and the closing line "For on_request properties, tell the traveller that the owner replies personally" restates "The owner replies personally" from earlier, a small redundancy tolerated for the operational detail it carries.

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?

Covers everything needed for a 5-parameter read tool with an output schema: what is returned, how to present instant vs on_request results, how to treat price vs price_total with breakdown, link labelling in the traveller's language, and the follow-up call to check_availability. Nothing an agent needs to call and present results correctly 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 coverage is 80%, so the baseline is 3, and the description earns above that: property_key is tied to search results, check_in/check_out determine whether price_breakdown or availability_note is returned, and lang/TEXT LANGUAGE governs output. Only guests lacks any explanation anywhere.

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 with scope: "Full details for one property by property_key (from search results)", then enumerates exactly what comes back (description, amenities, photos, house rules, cancellation, reviews, price_breakdown/availability_note). An agent knows precisely what this tool returns and how it differs from search tools.

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?

Gives explicit when-to-use and next-step routing: "When no dates are given... Always ask the traveller for dates, then call check_availability", naming the sibling. Also sets when-not guidance implicitly by distinguishing the instant vs on_request paths and what to do in each case.

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.