Skip to main content
Glama

Côte Privée: private driver in Burgundy

Prices

get_prices
Read-onlyIdempotent

Every price per vehicle, taxes, tolls and parking included: the cars (the Polestar 2, 4 guests, included; a Mercedes E-Class or V-Class, up to 7, on request for a supplement per day of service), wine days and which one a place needs by its distance (wineDayByDistance), driver by the hour, trips from Beaune and same-day returns, transfers, and when the price is paid (in full, once the driver confirms). Tastings are paid to the estates.

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": "get_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoar: Arabic notes, data in English.

Output Schema

NameRequiredDescriptionDefault
carsYes
paymentYes
updatedYes
vehicleYes
currencyYes
wineDaysYes
maxGuestsYes
transfersYes
perVehicleYes
pricesPageYes
tastingsNoteNo
validThroughYes
taxesIncludedYes
driverByTheHourYes
tripsFromBeauneYes
tastingsIncludedYes
wineDayByDistanceYes
tollsAndParkingIncludedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedOutput schema / properties / cars / items / properties / bags
      Added value: +{
      +  "properties": {
      +    "cabin": {
      +      "type": "integer"
      +    },
      +    "large": {
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "large",
      +    "cabin"
      +  ],
      +  "type": "object"
      +}
    • changedOutput schema / properties / cars / items / required
      Previous value: -[
      -  "id",
      -  "name",
      -  "seats",
      -  "included",
      -  "onRequest",
      -  "supplementPerDay",
      -  "rideBase",
      -  "ridePerKm"
      -]New value: +[
      +  "id",
      +  "name",
      +  "seats",
      +  "bags",
      +  "included",
      +  "onRequest",
      +  "supplementPerDay",
      +  "rideBase",
      +  "ridePerKm"
      +]
    • removedOutput schema / properties / depositRate
      Removed value: -{
      -  "type": "number"
      -}
    • addedOutput schema / properties / payment
      Added value: +{
      +  "enum": [
      +    "in full when the driver confirms"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "updated",
      -  "validThrough",
      -  "currency",
      -  "perVehicle",
      -  "maxGuests",
      -  "vehicle",
      -  "cars",
      -  "taxesIncluded",
      -  "tollsAndParkingIncluded",
      -  "tastingsIncluded",
      -  "depositRate",
      -  "wineDays",
      -  "wineDayByDistance",
      -  "driverByTheHour",
      -  "tripsFromBeaune",
      -  "transfers",
      -  "pricesPage"
      -]New value: +[
      +  "updated",
      +  "validThrough",
      +  "currency",
      +  "perVehicle",
      +  "maxGuests",
      +  "vehicle",
      +  "cars",
      +  "taxesIncluded",
      +  "tollsAndParkingIncluded",
      +  "tastingsIncluded",
      +  "payment",
      +  "wineDays",
      +  "wineDayByDistance",
      +  "driverByTheHour",
      +  "tripsFromBeaune",
      +  "transfers",
      +  "pricesPage"
      +]
  2. Changed3 schema fields changed
    • addedOutput schema / properties / cars / items / properties / rideBase
      Added value: +{
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / cars / items / properties / ridePerKm
      Added value: +{
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / cars / items / required
      Previous value: -[
      -  "id",
      -  "name",
      -  "seats",
      -  "included",
      -  "onRequest",
      -  "supplementPerDay"
      -]New value: +[
      +  "id",
      +  "name",
      +  "seats",
      +  "included",
      +  "onRequest",
      +  "supplementPerDay",
      +  "rideBase",
      +  "ridePerKm"
      +]
  3. Changed1 schema field changed
    • addedOutput schema / properties / transfers / items / properties / floor
      Added value: +{
      +  "type": "boolean"
      +}
  4. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description does add genuine business context beyond that — that tastings are excluded and paid to the estates, and that payment is due in full once the driver confirms — but it never says whether the tool returns a static catalog or a computed figure, nor how the lang parameter affects output.

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?

One long run-on sentence built from parenthetical fragments ('the cars (the Polestar 2, 4 guests, included; a Mercedes E-Class or V-Class...'), with no front-loaded statement of function. The reader has to parse it twice to extract that it is about pricing at all.

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

Completeness2/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, but the description still leaves the core question unanswered: is this a reference rate card or a computed quote, and how does it relate to `quote`? For a pricing tool with ten siblings, that ambiguity is material.

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?

There is a single optional parameter with a fully documented enum in the schema (including the note that Arabic returns English data with Arabic notes). The description adds nothing about it, but baseline 4 applies at 100% schema coverage with one param.

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

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The content is unambiguously about pricing (per-vehicle rates, supplements, wine-day pricing by distance, hourly driver, transfers), but it never states the operation as a verb+resource — there is no 'returns the price list for...' sentence. It also fails to distinguish itself from the sibling `quote`, which an agent would plausibly reach for when pricing a trip.

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

Usage Guidelines2/5

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

No statement of when to call this versus `quote`, `get_policies`, or `plan_wine_day`, and no prerequisites or exclusions. The agent must infer from the enumeration that this is the reference price catalog, which is guesswork.

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