Skip to main content
Glama

Search vacation rentals

search_properties
Read-onlyIdempotent

Find vacation rentals in a municipality or region (Italy, Germany, Spain, France, Portugal) for a number of guests. Where: municipality, province, (Italy) region, or a radius around an Italian municipality (near) or a point (latitude/longitude), each hit with its straight-line distance; the order stays tier, then name, sort by distance yourself. Criteria: capacity, bedrooms, bathrooms, amenities (a fixed table of names incl. pool facets such as private or heated, otherwise exact), what is rented, pets allowed, highest indicative price and, with from/to, dates not blocked in the operator's synced calendar. A stated fact that contradicts a criterion always leaves the property out. Each hit lists the criteria a stated fact meets in matched and says match (every criterion met) or possible, with the open points in unknown: by default only availability on request and a heated pool's heating on the requested dates; with include_possible also any fact the operator did not state (no current calendar is never read as free). Ask the operator about every point in unknown before relying on it. At most 20 results, ordered by the strongest free tier, then name (with include_possible matches first); the paid tier L5 does not change the order. No ranking by anything else, no fuzzy matching. Each result has priceFrom (indicative, negotiated directly, no booking) and the next window not blocked in the operator's calendar. Availability is a hint, never a booking commitment: a night not blocked in the operator's synced calendar may already be taken, since the calendar is a copy that can lag behind; only the operator confirms availability, and Ospitario holds or books nothing. Prices are indicative, stated by the host (on an unclaimed passport: taken from the official website), negotiated directly with the host; there is no booking through Ospitario. Every result is a property with a proven listing (L2/L2c), a verified operator (L3), a right to manage verified by document review (LA) or, marked L0 and unclaimed, facts from the operator's official website with nothing proven; the result names the tier and the date it was reached, and whether the registration number (Italy: CIN) was checked against the public register. Contact is direct with the operator and commission-free, so the traveler pays no platform fee. No result means nothing proven matches; nothing is inferred, estimated or filled in.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoCheckout date YYYY-MM-DD; requires from
fromNoCheck-in date YYYY-MM-DD; requires to
langNoLanguage of labels in the result; defaults to en
nearNoItalian municipality to search around, by name (e.g. Lecce); with radiusKm. A name several municipalities carry needs nearProvince
petsNotrue: only properties whose operator states that pets are allowed
guestsNoNumber of guests; properties with a lower capacity are left out. Optional since 1.14.0: without it, capacity is not a criterion
regionNoItalian region, by its Italian name or slug (Abruzzo, Basilicata, Calabria, Campania, Emilia-Romagna, Friuli-Venezia Giulia, Lazio, Liguria, Lombardia, Marche, Molise, Piemonte, Puglia, Sardegna, Sicilia, Toscana, Trentino-Alto Adige, Umbria, Valle d’Aosta, Veneto); the usual English, German, French, Spanish and Portuguese names are understood too (Apulia, Toskana). Italy only; matches the passport's province
countryNoISO 3166-1 alpha-2 country code: IT, DE, ES, FR or PT
bedroomsNoMinimum number of bedrooms
childrenNotrue: only properties whose operator states that children are welcome
latitudeNoPoint to search around, WGS 84 degrees; with longitude and radiusKm, instead of near
maxPriceNoHighest indicative price per night in EUR: properties whose lowest current or future priceFrom is above it, or that gave no price, are left out
provinceNoRegion code within the country, ISO 3166-2 without the prefix: IT/ES province (LE), FR département (75), DE Land (HH), PT distrito (11)
radiusKmNoRadius around near or latitude/longitude in km, straight line, default 20. A passport counts at its published exact location, else at its municipality's centre (computed from Istat's boundaries), so a home just inside a municipality can lie a few km off; every hit names its distance and basis. Municipality centres computed by Ospitario from Istat, Confini delle unità amministrative a fini statistici al 1° gennaio 2026 (CC BY 4.0)
stepFreeNotrue: only properties whose operator states step-free access
amenitiesNoEvery listed amenity must be present. These names match the operator's wording in any of the six languages through a fixed table: pool, wifi, parking, airConditioning (ac), garden, seaView, terrace, kitchen, washingMachine (washerDryer), bbq (outdoorGrill), heating, fireplace, balcony, tv, hotTub, elevator, crib, microwave, workspace. A pool can be asked with its facets: "private pool", "shared pool", "heated pool", "indoor pool", "outdoor pool" (or the same words in Italian, German, Spanish, Portuguese, French); a facet the operator did not state is unknown, not a match. Any other word must match an amenity exactly (case-insensitive).
bathroomsNoMinimum number of bathrooms; a half bath counts 0.5
longitudeNoPoint to search around, WGS 84 degrees; with latitude
placeKindNoentire, private_room or shared_room; properties that did not state it are left out
municipalityNoExact municipality name, e.g. Lecce
nearProvinceNoProvince code of near when the name is ambiguous (e.g. LE)
propertyKindNoKind of building: apartment, house, villa, farmhouse, trullo, cottage, chalet, other; a property that did not state it is open (unknown: propertyKind), another kind leaves it out
include_possibleNotrue: also return possible matches, where a requested fact is not stated (capacity, bedrooms, an amenity or pool facet, pets, price, current calendar) and nothing stated contradicts the request; each hit names the open points in unknown. Default false: only hits that meet every criterion, plus availability on request.

Output Schema

NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / guests / description
      Previous value: -"Number of guests; properties with a lower capacity are left out"New value: +"Number of guests; properties with a lower capacity are left out. Optional since 1.14.0: without it, capacity is not a criterion"
    • removedInput schema / required
      Removed value: -[
      -  "guests"
      -]
  2. Changed1 schema field changed
    • changedOutput schema / properties / results / items / properties / verification / properties / tier / description
      Previous value: -"Verification tier (docs: ADR 0012, 0017, 0024, 0025). L0 unclaimed: facts read from the operator's official website, nothing proven, the operator has not claimed the page; contact only through send_inquiry. L2 listing verified: the operator proved control of the platform listing (calendar export link with the listing id, platform email with a valid DKIM signature, or channel manager); since 2026-11-07 also their right to manage the property (LA or L3), and earlier L2 stands as it was reached. L2c listing calendar proven (Booking, Vrbo): the operator blocked a random date Ospitario named in that platform's calendar export within 48 hours; no new L2c since 2026-11-07. LA right to manage verified (document review): Ospitario's admin checked documents tying the operator to this property (registration record, deed, lease, mandate or company register); a person found them consistent, without eID, so it does not prove who holds the account and never proves a platform listing. L3 operator verified: the operator's eID identity (SPID/CIE) matches the CIN holder in the national register's PDF. L4 document verified (automated check): an ownership, lease or mandate document is consistent with that identity and the property; it states consistency, not authenticity. L5 manually verified: a reviewer checked the document (an optional upgrade; it does not affect search order)."New value: +"Verification tier (docs: ADR 0012, 0017, 0024, 0025). L0 unclaimed: facts read from the operator's official website, nothing proven, the operator has not claimed the page; contact only through send_inquiry. L2 listing verified: the operator proved control of the platform listing (calendar export link with the listing id, platform email with a valid DKIM signature, or channel manager); since 2026-11-07 also their right to manage the property (LA or L3), and earlier L2 stands as it was reached. L2c listing calendar proven (Booking, Vrbo): the operator blocked a random date Ospitario named in that platform's calendar export within 48 hours; no new L2c since 2026-11-07. LA right-to-manage documents reviewed: Ospitario's admin checked documents tying the operator to this property (registration record, deed, lease, mandate or company register); a person found them consistent, without eID, so it does not prove who holds the account and never proves a platform listing. L3 operator verified: the operator's eID identity (SPID/CIE) matches the CIN holder in the national register's PDF. L4 document verified (automated check): an ownership, lease or mandate document is consistent with that identity and the property; it states consistency, not authenticity. L5 manually verified: a reviewer checked the document (an optional upgrade; it does not affect search order)."
  3. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses critical behavior: availability is only a hint because the synced calendar can lag, prices are indicative and negotiated directly, results carry provenance tiers (L2/L2c, L3, LA, L0), and Ospitario holds or books nothing. This is exactly the kind of trust and limitation context an agent needs before relying on results.

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

Conciseness2/5

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

The description is a very long, dense stream of run-on sentences. Key points are front-loaded, but there is repetition (availability is a hint / no booking through Ospitario is stated multiple times) and several clauses could be trimmed without losing meaning.

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?

For a 23-parameter search tool with complex matching, tiering, and availability semantics, the description covers the essential mental model: what counts as a match, what 'possible' means, how unknown facts are surfaced, and what the results represent. The output schema handles return structure, so nothing critical is missing.

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%, so the baseline is 3. The description adds some semantic color (amenity facets, the fixed six-language table, the exclusion behavior for contradicting facts) but largely restates what the schema already documents, so it does not substantially outperform the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Find vacation rentals') and scopes it by geography and guest count, which is clear enough for an agent to identify the tool. It does not explicitly differentiate itself from the sibling tools (get_passport, list_places, lookup_by_name, etc.), but the purpose is unambiguous on its own.

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 gives clear operating context: default behavior returns only fully matching properties, include_possible widens to 'possible' hits, and it explicitly says not to rank by anything else and that there is no fuzzy matching. It lacks an explicit 'use this instead of X' alternative, but the when-to-use conditions are well defined.

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