Skip to main content
Glama

Côte Privée: private driver in Burgundy

Exact price for a trip

quote
Read-onlyIdempotent

The exact price the booking page charges for one service, or a whole trip (items: one total, paid in full once the driver confirms), the page of the priced service to cite (url; pricesUrl: every price) and a link that opens the booking page filled in (time, guests and bags too). Wine day: option and stops; a day too short for its stops is priced as the one they need (optionRaised). Driver: hours (and stops); with to, a ride there from Beaune or from; returnTrip: the driver waits up to 3 h; returnLater: back later (2 rides). Transfer, a ride from any starting point or place to any other: route (its id, its page slug such as lyon-beaune, or a name such as "Lyon airport"), or from and to; direction from: the way back (Meursault → Paris for a flight), at the same fare; stop: a stop on the way; back: the way back; a ride from or to Paris or Lyon never costs less than its route to Beaune, and from or to paris never comes back the same day. A Mercedes adds its supplement per day of service; over 4 guests, the V-Class (carRaised). resolved: what each name became (an unknown place or route is an error with candidates); alternatives: cheaper products for the same job; availability: with date.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoA place id or name, or event:<id>; for a ride a starting point too ("Lyon airport", "geneva").
carNopolestar (included), eclass (4 guests) or vclass (7): the Mercedes on request, a supplement per day of service.
backNoA ride's way back, instead of returnTrip: wait or later the same day (never from or to paris), day another day (returnDate).
dateNo
fromNoStart of a ride (service transfer, or the driver to one place): a station, an airport (airfields by ICAO code), Paris, Lyon, Geneva, Mâcon-Loché TGV (macon), Chalon-sur-Saône (chalon) or a city beyond Burgundy (reims, epernay, troyes, colmar, strasbourg, besancon, arbois, annecy, chamonix, avignon). A wine day: dijon, a full or long day from Dijon and back there, at its price.
langNoar: Arabic notes, data in English.
stopNoA ride's stop on the way (a tasting, a lunch): a place id or name; stopHours 1 to 3, each at the hourly price, plus the detour.
timeNoPickup (a transfer to Beaune: the arrival).
hoursNoDriver by the hour.
itemsNoSeveral services (at most 6), each with the fields above.
notesNoFor the driver: estates to visit, child seats…
routeNoA transfer route, by id or page slug (lyon (lyon-beaune), paris (paris-beaune), dijon (dijon-beaune), geneva (geneva-beaune), creusot (le-creusot-tgv-beaune), lfsd (dijon-airport-beaune), lfgj (dole-jura-airport-beaune)) or by name ("Lyon airport", "Dijon-Bourgogne", "Dole"): a transfer to or from Beaune (creusot: Le Creusot TGV; lfsd, lfgj: the airports).
stopsNoPlaces of a wine day, or of the driver by the hour.
guestsNo4 in the Polestar 2 or the E-Class, 7 in the V-Class.
optionNoWine day: half 4 h, full 8 h, long 12 h.
luggageNoBags.
serviceNo
directionNoA ride: to Beaune or the place (default), or from it: from paris, to village:meursault, direction from is Meursault → Paris (CDG, Orly or the city), at the same fare.
stopHoursNo
extraHoursNoWine day; default what its stops need.
returnTripNoDriver to a place: back the same day, the driver waiting. Transfer: a trip back another day.
returnLaterNoDriver to a place: back later the same day (two rides).

Output Schema

NameRequiredDescriptionDefault
carYes
urlYes
dateNo
fitsNo
timeNo
driveNo
priceYes
titleYes
guestsYes
optionNo
balanceNo
bookUrlYes
depositYes
detailsYes
luggageNo
paymentYes
serviceYes
currencyYes
notFoundYes
resolvedYes
servicesNo
carRaisedNo
maxGuestsYes
pricesUrlYes
extraHoursNo
perVehicleYes
alternativesNo
availabilityNo
optionRaisedNo
servicePriceYes
tastingsIncludedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedOutput schema / properties / balance / deprecated
      Added value: +true
    • addedOutput schema / properties / deposit / deprecated
      Added value: +true
    • addedOutput schema / properties / payment
      Added value: +{
      +  "enum": [
      +    "in full when the driver confirms"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "service",
      -  "title",
      -  "details",
      -  "price",
      -  "servicePrice",
      -  "car",
      -  "currency",
      -  "perVehicle",
      -  "guests",
      -  "maxGuests",
      -  "deposit",
      -  "tastingsIncluded",
      -  "resolved",
      -  "notFound",
      -  "url",
      -  "pricesUrl",
      -  "bookUrl"
      -]New value: +[
      +  "service",
      +  "title",
      +  "details",
      +  "price",
      +  "servicePrice",
      +  "car",
      +  "currency",
      +  "perVehicle",
      +  "guests",
      +  "maxGuests",
      +  "payment",
      +  "deposit",
      +  "tastingsIncluded",
      +  "resolved",
      +  "notFound",
      +  "url",
      +  "pricesUrl",
      +  "bookUrl"
      +]
  2. Changed9 schema fields changed
    • addedInput schema / properties / back
      Added value: +{
      +  "description": "A ride's way back, instead of returnTrip: wait or later the same day (never from or to paris), day another day (returnDate).",
      +  "enum": [
      +    "none",
      +    "wait",
      +    "later",
      +    "day"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / direction / description
      Previous value: -"Transfer: to Beaune or the place (default), or from it: from paris, to village:meursault, direction from is Meursault → Paris (CDG, Orly or the city), at the same fare."New value: +"A ride: to Beaune or the place (default), or from it: from paris, to village:meursault, direction from is Meursault → Paris (CDG, Orly or the city), at the same fare."
    • changedInput schema / properties / from / description
      Previous value: -"Start of a driver trip, or of a transfer to another place; airfields by ICAO code."New value: +"Start of a ride (service transfer, or the driver to one place): a station, an airport (airfields by ICAO code), Paris, Lyon, Geneva, Mâcon-Loché TGV (macon), Chalon-sur-Saône (chalon) or a city beyond Burgundy (reims, epernay, troyes, colmar, strasbourg, besancon, arbois, annecy, chamonix, avignon). A wine day: dijon, a full or long day from Dijon and back there, at its price."
    • 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 / returnLater / description
      Previous value: -"Driver: back later the same day (two rides)."New value: +"Driver to a place: back later the same day (two rides)."
    • changedInput schema / properties / returnTrip / description
      Previous value: -"Driver: back the same day, the driver waiting. Transfer: a trip back another day."New value: +"Driver to a place: back the same day, the driver waiting. Transfer: a trip back another day."
    • addedInput schema / properties / stop
      Added value: +{
      +  "description": "A ride's stop on the way (a tasting, a lunch): a place id or name; stopHours 1 to 3, each at the hourly price, plus the detour.",
      +  "maxLength": 120,
      +  "type": "string"
      +}
    • addedInput schema / properties / stopHours
      Added value: +{
      +  "maximum": 3,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • changedInput schema / properties / to / description
      Previous value: -"A place id or name, or event:<id>."New value: +"A place id or name, or event:<id>; for a ride a starting point too (\"Lyon airport\", \"geneva\")."
  3. Changed1 schema field changed
    • addedInput schema / properties / direction
      Added value: +{
      +  "description": "Transfer: to Beaune or the place (default), or from it: from paris, to village:meursault, direction from is Meursault → Paris (CDG, Orly or the city), at the same fare.",
      +  "enum": [
      +    "to",
      +    "from"
      +  ],
      +  "type": "string"
      +}
  4. Changed8 schema fields changed
    • changedInput schema / properties / route / description
      Previous value: -"Transfer to or from Beaune (creusot: Le Creusot TGV; lfsd, lfgj: airports)."New value: +"A transfer route, by id or page slug (lyon (lyon-beaune), paris (paris-beaune), dijon (dijon-beaune), geneva (geneva-beaune), creusot (le-creusot-tgv-beaune), lfsd (dijon-airport-beaune), lfgj (dole-jura-airport-beaune)) or by name (\"Lyon airport\", \"Dijon-Bourgogne\", \"Dole\"): a transfer to or from Beaune (creusot: Le Creusot TGV; lfsd, lfgj: the airports)."
    • removedInput schema / properties / route / enum
      Removed value: -[
      -  "lyon",
      -  "paris",
      -  "dijon",
      -  "geneva",
      -  "creusot",
      -  "lfsd",
      -  "lfgj"
      -]
    • addedInput schema / properties / route / maxLength
      Added value: +120
    • addedOutput schema / properties / pricesUrl
      Added value: +{
      +  "format": "uri",
      +  "type": "string"
      +}
    • addedOutput schema / properties / services / items / properties / url
      Added value: +{
      +  "format": "uri",
      +  "type": "string"
      +}
    • changedOutput schema / properties / services / items / required
      Previous value: -[
      -  "service",
      -  "title",
      -  "details",
      -  "servicePrice"
      -]New value: +[
      +  "service",
      +  "title",
      +  "details",
      +  "servicePrice",
      +  "url"
      +]
    • addedOutput schema / properties / url
      Added value: +{
      +  "format": "uri",
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "service",
      -  "title",
      -  "details",
      -  "price",
      -  "servicePrice",
      -  "car",
      -  "currency",
      -  "perVehicle",
      -  "guests",
      -  "maxGuests",
      -  "deposit",
      -  "tastingsIncluded",
      -  "resolved",
      -  "notFound",
      -  "bookUrl"
      -]New value: +[
      +  "service",
      +  "title",
      +  "details",
      +  "price",
      +  "servicePrice",
      +  "car",
      +  "currency",
      +  "perVehicle",
      +  "guests",
      +  "maxGuests",
      +  "deposit",
      +  "tastingsIncluded",
      +  "resolved",
      +  "notFound",
      +  "url",
      +  "pricesUrl",
      +  "bookUrl"
      +]
  5. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered; the description adds real behavioral rules beyond that: minimum fares ('a ride from or to Paris or Lyon never costs less than its route to Beaune'), the Mercedes per-day supplement, the V-Class uplift over 4 guests, the 3-hour wait cap on returnTrip, and that an unknown place or route is an error returning candidates. It loses a point for scattering these facts rather than stating them as constraints, and for partially restating output fields (resolved, alternatives) that the output schema already defines.

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

Conciseness2/5

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

Nearly the entire description is a single run-on sentence of semicolon-chained fragments, dense with domain-specific shorthand ('optionRaised', 'carRaised', 'Meursault → Paris for a flight'). The purpose is front-loaded, but the remainder is unstructured and forces the reader to parse rather than scan, so structure costs it here.

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?

The tool is complex (22 parameters, three service modes), and the output schema plus 86% parameter coverage already absorb return values and field semantics. The description does map the three service modes and their key inputs, which is necessary context, but it omits the routing decision against siblings and leaves the cross-mode interaction (items, nested services) largely implicit.

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?

With 86% schema description coverage, the schema already documents nearly every parameter including enum meanings such as option (half/full/long) and back (none/wait/later/day). The description mostly echoes those definitions ('route (its id, its page slug such as lyon-beaune, or a name...)', 'direction from: the way back') rather than adding syntax or defaults the schema lacks. Baseline 3 is appropriate when the schema carries the parameter load.

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 opening clause states a specific operation and resource: 'the exact price the booking page charges for one service, or a whole trip.' That is clearly a pricing/quote tool and distinguishable from list-style siblings like get_prices or plan_wine_day. It stops short of naming a sibling to contrast against, and the rest of the sentence buries the purpose under domain jargon.

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

Usage Guidelines3/5

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

Usage guidance is implied only through service branches ('Wine day: option and stops', 'Driver: hours', 'Transfer, a ride from any starting point...'), which tells an agent which fields to fill for each mode but never states when to call quote versus get_prices, plan_wine_day, or check_availability. The closing mention of 'availability: with date' gestures at a sibling handoff without spelling it out.

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