Skip to main content
Glama

Airsockfly

Create booking

create_booking
Idempotent

Reserve an offer for the user: re-prices the offer, holds availability and creates an order awaiting payment. Ask the user to confirm the offer, travellers and contact details first. When the result is price_changed, show the new price and call accept_price_change only if the user agrees.

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": {
      "vertical": "<vertical>",
      "externalId": "<externalId>",
      "travellers": "<travellers>",
      "contact": "<contact>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "create_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
contactYesContact details for booking confirmations.
endDateNoEnd date of the service, YYYY-MM-DD, when the offer does not fix it.
currencyNoCharge currency as an ISO 4217 code. Defaults to PLN.
verticalYesService type.
startDateNoStart date of the service, YYYY-MM-DD, when the offer does not fix it.
couponCodeNoDiscount code.
externalIdYesOffer identifier (externalId) returned by a search tool.
travellersYesPeople travelling or insured. The first one is the lead traveller and the main driver.
vehiclePlateNoVehicle registration number. Required for parking.
idempotencyKeyYesUnique key of 8 to 100 characters that you generate once per attempt. Repeating it never creates a duplicate.
insuranceAddonNoOptional travel insurance variant added to the booking.
driverLicenseYearsNoYears the main driver has held a driving licence.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, openWorldHint=true and destructiveHint=false, yet the description still adds real value: it discloses the side effects (re-pricing, holding availability, creating an unpaid order) and a result-state branch. It stops short of stating hold expiry, permission/auth requirements, or what happens on failure, so it is strong but not exhaustive.

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?

Three short sentences, front-loaded with the effect of the call followed by the confirmation requirement and the price_changed branch. Little waste, though the middle and final sentences could be tightened into one conditional clause.

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 12-parameter, nested-object mutation with no output schema, the description conveys the main effect and one important result state (price_changed) that the schema cannot express. It omits what a successful response contains and does not explicitly route to start_payment after the order is created, leaving that step inferable from the otherwise strong text.

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 every parameter is already documented at the field level, and the description's mention of "offer, travellers and contact details" maps onto existing fields without adding syntax or constraints. Baseline 3 is appropriate; the description does not deepen parameter meaning beyond 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?

The description states a specific verb and resource plus the internal effect: "Reserve an offer... re-prices the offer, holds availability and creates an order awaiting payment." It also names the sibling it hands off to (accept_price_change), so an agent can distinguish this from search_* tools and start_payment without opening another schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit preconditions ("Ask the user to confirm the offer, travellers and contact details first") and a conditional branch ("When the result is price_changed, show the new price and call accept_price_change only if the user agrees"). Both when-to-use and when-not-to-proceed are covered rather than implied.

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