Skip to main content
Glama

La Palme d'Azur Cannes: hotel, aparthotel & resort

Live availability and exact prices

search_availability
Read-onlyIdempotent

Live availability and exact prices (EUR, city tax excluded) for a stay at Residence La Palme d'Azur Cannes Verrerie (hotel, aparthotel and resort apartments in Cannes, French Riviera). Call it as soon as the traveller gives dates; never estimate a price. Returns one entry per apartment type with is_available, min_stay, price_per_night, total_price, page_url and a booking_url that opens the official booking page with dates and guests prefilled. When nothing is available, alternatives lists up to 3 nearby stays of the same length. units_left appears only when 1-2 units remain; its absence does not mean sold out. Prices come from the official booking engine in real time and may change until the booking is confirmed.

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": {
      "check_in": "<check_in>",
      "check_out": "<check_out>"
    },
    "name": "search_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the booking page to link to (fr = /fr-fr/reserver, others = /{lang}/book).fr
adultsNoNumber of adults (1-20).
check_inYesArrival date, YYYY-MM-DD, today or later (Europe/Paris).
childrenNoNumber of children (0-20). Changes the price: always pass it when known.
check_outYesDeparture date, YYYY-MM-DD, after check_in, at most 30 nights later.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing that prices come from the official booking engine in real time and may change until confirmation, that city tax is excluded, and that `units_left` only appears at 1-2 remaining units with absence not implying sold out — a genuinely non-obvious semantic trap. The fallback behavior of up to 3 `alternatives` of the same length is also disclosed.

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 purpose and the imperative call rule, then return fields, then edge cases — a sensible information hierarchy with no filler sentences. It is dense and long-ish for a five-parameter read tool, but nearly every clause carries operational value (currency, tax, units_left caveat).

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?

With no output schema, the description carries the full burden of describing returns and does so field-by-field, plus the conditional `units_left` and `alternatives` behaviors. For a read-only pricing tool this leaves nothing an agent needs missing before calling it.

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 coverage is 100%, so every parameter's meaning, bounds, date format and the 30-night limit are already documented in the schema. The description adds only indirect context (dates and guest counts prefilled into booking_url) and no parameter-level detail beyond the schema, so the baseline 3 applies.

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 — live availability and exact prices in EUR for a named property — and enumerates the returned fields (is_available, min_stay, price_per_night, total_price, page_url, booking_url). This clearly distinguishes it from siblings like list_apartments (catalog) and build_booking_link (URL construction), since this one answers 'can I book and at what price'.

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?

Gives explicit triggering guidance: 'Call it as soon as the traveller gives dates; never estimate a price,' which tells the agent both when to invoke and what not to substitute for it. It also covers the empty-result path via `alternatives`. It stops short of naming sibling tools by name for the cases they cover, keeping it at a strong 4 rather than a 5.

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