Skip to main content
Glama

Discover Canal Cruises – private tours in Leiden

Create booking link

create_booking_link

Checks that the time is still free and returns a secure booking link with tour, date, time, guests and extras already filled in. Give this link to the guest: they check the details and pay there. Guest details are optional ('guest'): pass them only if the guest gave them to you for this booking; then name, e-mail and/or phone are filled in on the booking page. They are stored on our server for at most 24 hours and are not in the link itself. No e-mail is sent before payment; the guest confirms the booking by paying. Nothing is reserved or charged by this tool.

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": {
      "tour": "<tour>",
      "date": "<date>",
      "time": "<time>",
      "guests": "<guests>"
    },
    "name": "create_booking_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesTour date, YYYY-MM-DD.
timeYesStart time HH:MM, one of the free times from check_availability.
tourYesTour id (the "tour" value from list_tours, e.g. "cosy-tour").
guestNoOptional. Only if the guest gave you these for this booking. Each field is optional.
guestsYesNumber of guests in the group (adults and children together).
optionsNoOptional extras, keyed by option id (or option name) from get_tour. Value: the chosen text for a choice, true for a yes/no extra, a number for a quantity.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / guest
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Optional. Only if the guest gave you these for this booking. Each field is optional.",
      +  "properties": {
      +    "email": {
      +      "description": "E-mail address for the confirmation (sent only after payment).",
      +      "maxLength": 190,
      +      "type": "string"
      +    },
      +    "name": {
      +      "description": "Full name of the guest who books.",
      +      "maxLength": 160,
      +      "minLength": 2,
      +      "type": "string"
      +    },
      +    "phone": {
      +      "description": "Phone number with country code, e.g. +31 6 12345678.",
      +      "maxLength": 40,
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations are sparse (readOnlyHint=false, destructiveHint=false), so the description carries real weight and does: nothing is reserved or charged, the link is only paid on by the guest, no e-mail is sent before payment, and guest PII is stored server-side for at most 24 hours and is not embedded in the link. These are exactly the side-effect and privacy facts an agent needs before calling a non-idempotent creator that handles personal data.

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 outcome (what is returned) before the caveats, and each later sentence adds a distinct operational fact (consent rule, storage lifetime, no pre-payment e-mail, no charge). It is somewhat longer than needed — the optional-guest point is restated across two sentences — but nothing is filler.

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 non-idempotent creator with a nested optional guest object and no output schema, the description covers what is produced, what is and is not triggered, and the data-handling implications. It does not describe failure behavior (e.g. what happens if the slot is taken between check and call), which is the one gap an agent would still have to discover empirically.

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?

Schema coverage is 100%, so the baseline is 3; the description still adds meaning the schema cannot, explaining that 'guest' is optional and conditional on consent, what gets pre-filled on the page, and how long that data persists. 'extras already filled in' loosely maps to the options parameter but stops short of explaining how option values are keyed or typed, leaving that to the schema.

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 artifact ('returns a secure booking link with tour, date, time, guests and extras already filled in') and scopes it by explicitly saying 'Nothing is reserved or charged by this tool', which separates it from any actual booking/charging action. It also implies the relationship to availability checking ('Checks that the time is still free'), so an agent can place it in the flow without opening the 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 concrete when-to-use context: hand the link to the guest, who verifies and pays there, and states the condition for passing the optional guest object ('only if the guest gave them to you for this booking'). What is missing is an explicit pointer to a prerequisite sibling (e.g. that the time must come from check_availability) — that constraint lives only in the date/time schema descriptions, not the prose.

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