Skip to main content
Glama

BookResorts — hotel & resort booking

Create a checkout link

create_booking_link

Create a secure checkout link for one room option from get_hotel. Give the link to the traveller: it opens our checkout with that exact room, dates and price, where they enter their details and pay (rate re-confirmed live). Links last 24 hours. Never ask the traveller for card details yourself.

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": {
      "hotel_id": "<hotel_id>",
      "option_id": "<option_id>",
      "checkin": "<checkin>",
      "checkout": "<checkout>"
    },
    "name": "create_booking_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
roomsNo
adultsNo
checkinYesYYYY-MM-DD
checkoutYesYYYY-MM-DD
hotel_idYes
option_idYesoption_id from get_hotel
children_agesNo

Output Schema

NameRequiredDescriptionDefault
noteNo
roomYes
boardNo
hotelYes
refundableNo
booking_linkYesGive this URL to the traveller; it opens our secure checkout with the room, dates and price. Valid 24 hours.
total_price_usdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "board": {
      +      "type": "string"
      +    },
      +    "booking_link": {
      +      "description": "Give this URL to the traveller; it opens our secure checkout with the room, dates and price. Valid 24 hours.",
      +      "type": "string"
      +    },
      +    "hotel": {
      +      "type": "string"
      +    },
      +    "note": {
      +      "type": "string"
      +    },
      +    "refundable": {
      +      "type": "boolean"
      +    },
      +    "room": {
      +      "type": "string"
      +    },
      +    "total_price_usd": {
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "booking_link",
      +    "hotel",
      +    "room",
      +    "total_price_usd"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: links expire after 24 hours, the rate is re-confirmed live at checkout, and payment/data entry happens on the hosted page rather than in the agent's hands. None of this is derivable from readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false.

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

Conciseness5/5

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

Four short sentences, front-loaded with the action, then handoff instructions, then the two operational constraints (expiry, live rate). No redundant restatement of the title or schema.

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?

An output schema exists, so return values need not be described, and the handoff/expiry/payment behavior is fully covered. The only gap is the unaddressed guest-count parameters for a 7-param tool, which matters for a booking flow that prices by occupancy.

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 only 43%, so the description must compensate. It clarifies the semantics of hotel_id, option_id and the dates ('that exact room, dates and price'), but says nothing about the occupancy parameters rooms, adults and children_ages, leaving three of seven params unexplained in both schema and description.

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?

Specific verb+resource: 'Create a secure checkout link for one room option.' It names the sibling that supplies the input ('from get_hotel'), which both differentiates it from search_hotels and tells the agent where hotel_id/option_id must come from.

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 clear operational context: mint the link, hand it to the traveller, and never collect card details yourself. It does not explicitly state when-not to use this tool (e.g. for multi-room or multi-option bookings), but the 'one room option' scoping implies the boundary.

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