Skip to main content
Glama

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

Official direct-booking link

build_booking_link
Read-onlyIdempotent

Builds the official direct-booking URL of Residence La Palme d'Azur Cannes Verrerie with dates, guests and language prefilled, using only the parameters the booking page actually reads (arrive, depart, adults, children, optional room-type priority). Use it after search_availability or whenever the traveller wants to book. Parties of 8+ guests land on the multi-apartment group configurator. The link does not hold, price or reserve anything.

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": "build_booking_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the booking page to link to (fr = /fr-fr/reserver, others = /{lang}/book).fr
adultsNo
check_inYesArrival date, YYYY-MM-DD.
childrenNo
check_outYesDeparture date, YYYY-MM-DD.
room_type_codeNoOptional room_type_code (from list_apartments or search_availability) to show first on the booking page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety bar is low. The description still earns credit by adding that the link 'does not hold, price or reserve anything' and that parties of 8+ are routed to a group configurator, but it never states the return type (a URL string) or any failure mode for invalid dates.

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 core action in the first clause, and each of the three sentences carries information the agent needs. The parenthetical parameter list partly duplicates the schema, costing a little density.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers scope, sequencing, the 8+ group edge case and the fact that nothing is reserved, which is adequate for a 6-parameter link builder. With no output schema, it should have said explicitly that a URL string is returned.

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?

With 67% schema coverage, the description adds real meaning by naming which parameters the booking page actually reads and framing room_type_code as a 'priority' (display order) rather than a filter — a distinction the schema only hints at. Minor inconsistency: lang is mapped to a path segment in the schema but omitted from the 'parameters the page reads' list.

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 (builds), a specific resource (the official direct-booking URL for the named property), and its scope (dates, guests, language prefilled). An agent can distinguish it immediately from search_availability, get_property_facts and list_apartments without opening any schema.

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 an explicit trigger ('use it after search_availability or whenever the traveller wants to book') and names the sibling it follows. It lacks an explicit when-not statement (e.g. do not use for availability checks), though the closing note that it reserves nothing partly covers that.

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