Skip to main content
Glama

Côte Privée: private driver in Burgundy

Send a booking request

request_booking
Idempotent

Sends a booking request as the booking page does, once the traveller has seen the price and accepted the terms of sale (https://www.cote-privee.com/terms): one service (the fields of quote, with date, time and pickup), several (items) or a plan of find_trips (trip, startDate), and the traveller's details. Nothing is charged: the traveller gets the request by e-mail, and the driver confirms it by e-mail and says how to pay the full price, or declines it (next says it for this request; payment: "in full when the driver confirms"). dry_run checks and prices without sending; the same request within a day, or the same requestId, answers the same reference. Only valid requests count against the limits; a refusal names each argument to fix and what is allowed (retryAfter after a limit).

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": {
      "name": "<name>",
      "email": "<email>",
      "phone": "<phone>",
      "accept_terms": "<accept_terms>"
    },
    "name": "request_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
carNo
backNo
dateNo
fromNo
langNoar: Arabic notes, data in English.
nameYes
stopNo
timeNo
tripNoA plan id of find_trips.
emailYes
hoursNo
itemsNoSeveral services (at most 6), each with the fields above.
notesNo
phoneYes
routeNo
stopsNo
flightNoFlight or train.
guestsNo
optionNo
pickupNoPickup address (a hotel, a street) at the start of a ride or of the day.
dropoffNoA ride: where the car leaves the guests (a hotel).
dry_runNo
luggageNo
serviceNo
directionNo
requestIdNo8 to 64 letters, digits, - or _.
startDateNoThe plan's first day.
stopHoursNo
extraHoursNo
returnDateNo
returnTimeNo
returnTripNo
returnLaterNo
accept_termsYestrue only once the traveller has accepted the terms of sale.
returnFlightNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / package
      Removed value: -{
      -  "description": "A plan id of find_packages.",
      -  "maxLength": 80,
      -  "type": "string"
      -}
    • changedInput schema / properties / startDate / description
      Previous value: -"The package's first day."New value: +"The plan's first day."
    • addedInput schema / properties / trip
      Added value: +{
      +  "description": "A plan id of find_trips.",
      +  "maxLength": 80,
      +  "type": "string"
      +}
  2. Changed6 schema fields changed
    • addedInput schema / properties / back
      Added value: +{
      +  "enum": [
      +    "none",
      +    "wait",
      +    "later",
      +    "day"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / dropoff
      Added value: +{
      +  "description": "A ride: where the car leaves the guests (a hotel).",
      +  "maxLength": 300,
      +  "type": "string"
      +}
    • changedInput schema / properties / from / enum
      Previous value: -[
      -  "beaune",
      -  "dijon",
      -  "lyon",
      -  "paris",
      -  "geneva",
      -  "creusot",
      -  "lfsd",
      -  "lfgj",
      -  "lfgf",
      -  "lfgz",
      -  "lflh",
      -  "lfgi",
      -  "lfep"
      -]New value: +[
      +  "beaune",
      +  "dijon",
      +  "lyon",
      +  "paris",
      +  "geneva",
      +  "creusot",
      +  "lfsd",
      +  "lfgj",
      +  "lfgf",
      +  "lfgz",
      +  "lflh",
      +  "lfgi",
      +  "lfep",
      +  "macon",
      +  "chalon",
      +  "reims",
      +  "epernay",
      +  "troyes",
      +  "colmar",
      +  "strasbourg",
      +  "besancon",
      +  "arbois",
      +  "annecy",
      +  "chamonix",
      +  "avignon"
      +]
    • changedInput schema / properties / pickup / description
      Previous value: -"Pickup address (a hotel, a street); a transfer to Beaune: the drop-off."New value: +"Pickup address (a hotel, a street) at the start of a ride or of the day."
    • addedInput schema / properties / stop
      Added value: +{
      +  "maxLength": 120,
      +  "type": "string"
      +}
    • addedInput schema / properties / stopHours
      Added value: +{
      +  "maximum": 3,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  3. Changed1 schema field changed
    • removedInput schema / properties / direction / description
      Removed value: -"Transfer: to Beaune (default) or from it."
  4. Changed2 schema fields changed
    • removedInput schema / properties / route / enum
      Removed value: -[
      -  "lyon",
      -  "paris",
      -  "dijon",
      -  "geneva",
      -  "creusot",
      -  "lfsd",
      -  "lfgj"
      -]
    • addedInput schema / properties / route / maxLength
      Added value: +120
  5. First observed

TDQS

A3.7/5.0
Behavior5/5

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

The description adds substantial behavior beyond the annotations: nothing is charged, the traveller receives the request by e-mail, the driver confirms or declines by e-mail, and payment is handled after confirmation. It also discloses dry_run behavior, idempotency by requestId or same-day request, limit behavior, and refusal/retryAfter details.

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

Conciseness3/5

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

The purpose is front-loaded, but the rest is delivered as a single dense run-on paragraph with nested clauses, semicolons, and parentheticals. Much of the content is valuable, yet the structure makes it harder to scan than it needs to be.

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

Completeness3/5

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

It covers the core workflow, idempotency, dry-run behavior, and error/limit handling well. However, for a 36-parameter mutation with no output schema, it leaves too many parameter semantics and some return/confirmation details implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 36 parameters and only 25% schema description coverage, the description compensates only partially. It clarifies the three request shapes and a few key fields such as requestId, dry_run, accept_terms, trip, and startDate, but many important parameters (from, to, service, direction, back, hours, option, guests, luggage, etc.) remain unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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: it sends a booking request after price visibility and terms acceptance. It also names the supported request shapes (single service, items array, find_trips plan), which helps distinguish it from sibling pricing/search tools, though the phrasing is dense.

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?

It gives a clear precondition: use after the traveller has seen the price and accepted the terms. It also presents dry_run as the no-send alternative and explains idempotent retry behavior, but it does not explicitly route the agent to quote or get_prices beforehand.

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