Skip to main content
Glama

Côte Privée: private driver in Burgundy

Plan a wine day

plan_wine_day
Read-onlyIdempotent

A timed wine day through the places asked: its length (with the extra hours their distance needs), the stops in order, the drives from and back to Beaune (or from), lunch where the day reaches midday (at a starred table among the stops, else a slot with the starred tables near it), the end time, the price for the guests and their car (the V-Class beyond 4), the page of that wine day (url) and a booking link.

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": {
      "stops": "<stops>"
    },
    "name": "plan_wine_day"
  }
}

Input Schema

NameRequiredDescriptionDefault
carNopolestar (included), eclass (4 guests) or vclass (7): the Mercedes on request, a supplement per day of service.
dateNo
fromNoStart and end (default beaune).
langNoar: Arabic notes, data in English.
timeNoPickup.
lunchNo"yes", or a place to have lunch near.
stopsYesPlace ids or names.
guestsNo

Output Schema

NameRequiredDescriptionDefault
carYes
dayYes
endYes
urlYes
legsYes
noteYes
hoursYes
lunchNo
priceYes
startYes
stopsYes
guestsYes
bookUrlYes
depositYes
paymentYes
notFoundYes
resolvedYes
scheduleYes
pricesUrlYes
extraHoursYes
availabilityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • 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: -[
      -  "day",
      -  "extraHours",
      -  "hours",
      -  "start",
      -  "end",
      -  "guests",
      -  "car",
      -  "price",
      -  "deposit",
      -  "schedule",
      -  "legs",
      -  "stops",
      -  "resolved",
      -  "notFound",
      -  "url",
      -  "pricesUrl",
      -  "bookUrl",
      -  "note"
      -]New value: +[
      +  "day",
      +  "extraHours",
      +  "hours",
      +  "start",
      +  "end",
      +  "guests",
      +  "car",
      +  "price",
      +  "payment",
      +  "deposit",
      +  "schedule",
      +  "legs",
      +  "stops",
      +  "resolved",
      +  "notFound",
      +  "url",
      +  "pricesUrl",
      +  "bookUrl",
      +  "note"
      +]
  2. Changed1 schema field changed
    • 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"
      +]
  3. Changed3 schema fields changed
    • addedOutput schema / properties / pricesUrl
      Added value: +{
      +  "format": "uri",
      +  "type": "string"
      +}
    • addedOutput schema / properties / url
      Added value: +{
      +  "format": "uri",
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "day",
      -  "extraHours",
      -  "hours",
      -  "start",
      -  "end",
      -  "guests",
      -  "car",
      -  "price",
      -  "deposit",
      -  "schedule",
      -  "legs",
      -  "stops",
      -  "resolved",
      -  "notFound",
      -  "bookUrl",
      -  "note"
      -]New value: +[
      +  "day",
      +  "extraHours",
      +  "hours",
      +  "start",
      +  "end",
      +  "guests",
      +  "car",
      +  "price",
      +  "deposit",
      +  "schedule",
      +  "legs",
      +  "stops",
      +  "resolved",
      +  "notFound",
      +  "url",
      +  "pricesUrl",
      +  "bookUrl",
      +  "note"
      +]
  4. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety burden is light; the description goes beyond them by disclosing domain behavior: distance-derived extra hours, lunch resolution (starred table among the stops, else the nearest starred slot), and a car-dependent pricing rule (V-Class beyond 4). It still omits failure cases, how infeasible stop lists are reported, and whether the page url is stable.

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?

It is a single unbroken sentence with stacked parentheticals, so it is compact but not front-loaded or scannable — the agent must parse one long clause chain to find the core behavior. Roughly half of the text enumerates return values that the output schema already defines.

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?

For an 8-parameter planning tool, the description covers the itinerary logic but spends its length on return contents that the output schema already provides, while omitting ordering relative to sibling tools and how errors or infeasible combinations surface. Adequate, with clear gaps given the tool's complexity.

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 coverage is 75%, so the baseline is 3. The description does add meaning beyond the schema for lunch (the resolution rule, not just 'yes or a place') and for the car/price interaction, but it says nothing about date, time, guests, lang, or the 12-stop limit, leaving those entirely to the schema.

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 names a specific resource (a timed wine day itinerary built from the requested stops) and enumerates its outputs (length, ordered stops, drives, lunch, end time, price, page url, booking link), which is concrete enough to separate it from siblings like quote or get_prices. It never states the purpose as a verb phrase for the agent, but the outcome it produces is unambiguous.

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?

There is no statement of when to use this versus check_availability, quote, get_prices, search_places, or request_booking, and no prerequisites (e.g., whether places must first be resolved via search_places). Usage is only inferable from 'the places asked' and the booking link it returns.

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