Skip to main content
Glama

Create a link to complete the booking

crear_enlace_reserva

For clients explicitly using the legacy draft flow, prepares the selected car and extras and returns a single-use link to the pre-filled booking form on rentacar.canarias.com. Customer details are optional and included only with permission. The customer reviews current availability and the final price and completes the booking on the website. The link expires after at most 30 minutes, or sooner if the offer expires. The response contains enlace (the continuation URL), caducaEnMinutosMaximos (maximum validity in minutes), mensajeCliente (customer-facing text) and aviso (the reminder that completion takes place on the website). This tool does not book, charge or cancel.

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": {
      "idOferta": "<idOferta>"
    },
    "name": "crear_enlace_reserva"
  }
}

Input Schema

NameRequiredDescriptionDefault
extrasNoSelected extras by ID and quantity
clienteNoOptional customer details shared with permission
idOfertaYesOffer ID
pagoOnlineNoInitial payment preference; the customer can change it on the website

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / cliente / description
      Previous value: -"Datos opcionales facilitados con permiso del cliente / Optional customer details shared with permission"New value: +"Optional customer details shared with permission"
    • changedInput schema / properties / extras / description
      Previous value: -"Extras elegidos por ID y cantidad / Selected extras by ID and quantity"New value: +"Selected extras by ID and quantity"
    • changedInput schema / properties / extras / items / properties / cantidad / description
      Previous value: -"Cantidad / Quantity"New value: +"Quantity"
    • changedInput schema / properties / extras / items / properties / id / description
      Previous value: -"ID del extra / Extra ID"New value: +"Extra ID"
    • changedInput schema / properties / idOferta / description
      Previous value: -"Identificador opaco de la oferta / Opaque offer ID"New value: +"Offer ID"
    • changedInput schema / properties / pagoOnline / description
      Previous value: -"Preferencia inicial de pago; el cliente puede cambiarla en la web / Initial payment preference; the customer can change it on the website"New value: +"Initial payment preference; the customer can change it on the website"
  2. Changed1 schema field changed
    • changedInput schema / properties / idOferta / description
      Previous value: -"Identificador devuelto por buscar_disponibilidad / Offer ID"New value: +"Identificador opaco de la oferta / Opaque offer ID"
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only flag readOnly=false, openWorld=true, idempotent=false, destructive=false; the description adds substantial detail beyond that — the link is single-use, expires in at most 30 minutes or sooner if the offer expires, and no booking, charging or cancellation occurs. It also enumerates the four returned fields, so the agent knows what comes back despite no output schema.

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-loads the core action and scope, then expiration, then return values, then the non-mutation caveat — a sensible order. There is mild redundancy between 'completes the booking on the website' and the closing 'does not book, charge or cancel', but no wasted padding.

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?

For a four-parameter, open-world mutation that returns a URL, the definition covers expiry, single-use semantics, the returned fields and the no-side-effects guarantee. It does not say what happens when the offer has already expired or the link cannot be created, which is the one behavioral gap.

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 schema already documents idOferta, extras, cliente and pagoOnline, and the baseline is 3. The description mostly restates that customer details are optional and permission-gated, and never mentions pagoOnline's meaning, so it adds little beyond the structured fields.

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 — prepares the selected car and extras and returns a single-use link to a pre-filled booking form on a named domain — and scopes it to 'clients explicitly using the legacy draft flow'. The closing sentence 'This tool does not book, charge or cancel' further separates it from the availability/offer 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?

Gives a clear use condition ('For clients explicitly using the legacy draft flow') and a permission rule for customer data, which is real when-to-use guidance. It does not explicitly name an alternative path for non-legacy flows or state when not to use it, so it falls short of the top mark.

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