Skip to main content
Glama

Côte Privée: private driver in Burgundy

Booking rules and the car

get_policies
Read-onlyIdempotent

The booking rules as facts: the cars, the guests and the bags each takes, when the price is paid (in full, once the driver confirms), booking window and today in Beaune, service hours, luggage, waiting, cancellation, child seats, languages, the hours bookings are answered, the kind of licence and the SIREN, and the FAQ answers about them. A rule not published yet is null or left out.

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_policies"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoar: Arabic notes, data in English.

Output Schema

NameRequiredDescriptionDefault
carsYes
hoursYes
pagesYes
guestsYes
answersYes
bookingYes
depositYes
licenceYes
luggageYes
paymentYes
vehicleYes
waitingYes
languagesYes
childSeatsYes
termsFinalYes
cancellationYes
serviceHoursYes

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"
      +]
    • addedOutput schema / properties / deposit / deprecated
      Added value: +true
    • addedOutput schema / properties / payment
      Added value: +{
      +  "properties": {
      +    "answer": {
      +      "type": "string"
      +    },
      +    "when": {
      +      "enum": [
      +        "in full when the driver confirms"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "when",
      +    "answer"
      +  ],
      +  "type": "object"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "vehicle",
      -  "cars",
      -  "guests",
      -  "deposit",
      -  "booking",
      -  "serviceHours",
      -  "luggage",
      -  "waiting",
      -  "cancellation",
      -  "childSeats",
      -  "languages",
      -  "hours",
      -  "licence",
      -  "answers",
      -  "termsFinal",
      -  "pages"
      -]New value: +[
      +  "vehicle",
      +  "cars",
      +  "guests",
      +  "payment",
      +  "deposit",
      +  "booking",
      +  "serviceHours",
      +  "luggage",
      +  "waiting",
      +  "cancellation",
      +  "childSeats",
      +  "languages",
      +  "hours",
      +  "licence",
      +  "answers",
      +  "termsFinal",
      +  "pages"
      +]
  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. 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, closed-world, non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: 'A rule not published yet is null or left out,' telling the agent how to interpret missing fields instead of treating absence as an error. It does not discuss size of payload or caching, but the key caveat is present.

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 comma-spliced sentence of roughly a hundred words; the lead 'The booking rules as facts' is well front-loaded, but the long undifferentiated content list ('waiting, cancellation, child seats, languages, the hours bookings are answered...') is hard to scan. A bulleted or grouped structure would earn the same information at lower reading cost.

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?

An output schema exists, so return-value shape needn't be described, and the description instead enumerates the semantic coverage of the payload plus the null/omitted convention. What is missing is the 'use this instead of X' routing, which is more a usage-guideline gap than a completeness one.

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?

Only one optional parameter (lang) and schema description coverage is 100%, with the enum and the 'ar: Arabic notes, data in English' note fully documented in the schema. The description adds nothing about language selection, so baseline 3 applies.

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 'The booking rules as facts' plus the enumeration of contents (cars, guests, bags, price payment timing, booking window, service hours, cancellation, licence, SIREN, FAQ) makes clear this is the static policy/config retrieval tool. It is distinguishable from get_prices and check_availability by being a bundled rules dump rather than a computed quote, though it never names those siblings to draw the line explicitly.

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 call this versus get_prices, check_availability, get_page, or the FAQ-ish content it partially duplicates. An agent must infer from the content list alone that this is the reference lookup for pre-booking questions rather than a live availability or pricing check.

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