Skip to main content
Glama

Get a fixed-price quote

get_quote
Read-only

Exact fixed prices for a transfer between two locations, straight from the live booking engine. Per vehicle, AUD, GST and tolls included, locked at booking, no surge. If the route has no fixed price the response says so — never estimate a figure yourself. Every quote without stops includes book_url (and one per vehicle in book_urls): a pre-filled booking page the customer completes, accepts terms and pays on. Give the customer that link exactly as returned, utm tags included, so the booking is attributed to an AI assistant; pass date, time, passengers, return leg, luggage, child seats and flight here so the link carries them. With a date, closures are checked first: on a day the booking engine closes or inside one of its closed windows (holiday hours included) the response is available:false with the closure message and no prices. On a holiday-surcharge date (Christmas Day, Boxing Day, Easter Sunday) the prices include the surcharge, as the booking form charges it: holiday_surcharge and the notes say how much, and the price you give should say it includes it. fares_aud are always ONE-WAY fares; with return_date the quote adds return_totals_aud, the whole return trip per vehicle (outbound plus the return leg at the booking form's return discount) — quote that for a return, never the one-way fare. If the return starts or ends somewhere else (in to one hotel, back from another), add return_pickup and/or return_dropoff: each trip is then priced at its own fare and the return discount comes off the cheaper trip, exactly as the booking form does. Stops on the way (up to 4 each way): add stops, and return_stops for the way back on a return. The booking form adds the detour through them, charged by the extra distance and the same for every vehicle, and the quote gives totals_aud (one way) or return_totals_aud (a return) with the stops in: quote those. A quote with stops has no book_url (the booking form's links can't carry stops yet): book it with request_booking. Give hotels, venues and businesses as the customer named them, without adding a suburb yourself: every place goes through the booking system's address lookup, and a named place given with a suburb is checked against where Google finds it and priced where it really is (place_corrected and address_check say what to tell the customer). An airport pickup can only be booked with the flight number they land on: ask for it with the other booking details.

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": {
      "pickup": "<pickup>",
      "dropoff": "<dropoff>"
    },
    "name": "get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
paxNoTotal passengers including children. With pax the quote lists only the vehicles that take the whole group, as the booking engine does: groups of 8 or more get the two-vehicle options and the 12-seater Transporter (up to 11 passengers, one vehicle for the whole group).
bagsNoLarge bags (suitcases; a pram or stroller counts as one). Goes into book_url. The quote lists vehicles by passengers, so check the bags against the fleet in get_service_info: the Kia Carnival takes more when fewer people travel. With pax and bags, the Transporter is left out when the group has more large bags than it takes (up to 8 for 9-11 people): two vehicles take them.
dateNoTravel date YYYY-MM-DD (goes into book_url; closures are checked)
timeNoPickup time HH:MM, 24h, Queensland time (goes into book_url)
carryNoCarry-on bags
seatsNoChild seats as {index: qty}; index 0 rear-facing (0-3y), 1 forward-facing (6m-3y), 2 harnessed booster (3-6y), 3 booster with adult belt (6y+). $35 each.
stopsNoOptional: stops on the way (drop someone off, a shop, a second hotel), in order, up to 4. Each a street address (number and street, suburb) or a hotel or venue name with its suburb, never just a suburb. The booking form adds the detour through them, charged by the extra distance and the same for every vehicle. On a return these are the stops on the way there. Leave out for none.
flightNoFlight number, e.g. JQ430 (goes into book_url). An airport pickup is only booked with the flight number they land on.
pickupYesPickup suburb, hotel or airport
dropoffYesDrop-off suburb, hotel or airport
vehicleNoChosen vehicle: sedan | carnival | carnival_rav4 | two_carnivals | transporter (sets book_url; book_urls has all)
oversizedNoSurfboard, golf bag, bike box or similar (takes the space of three large bags, so the sedan drops out). Not for a pram or stroller: that is one large bag in bags, and it means the Carnival rather than the sedan.
return_dateNoReturn leg date YYYY-MM-DD, if a return: adds return_totals_aud (the whole return trip per vehicle)
return_timeNoReturn leg pickup time HH:MM
return_stopsNoOptional, with return_date: stops on the way back, in order, up to 4, same rules as stops. Not copied from stops: leave out for no stops on the way back.
return_pickupNoOptional, with return_date: where the return trip picks up, if not the first trip's drop-off (e.g. a different hotel). Defaults to the first trip reversed.
return_dropoffNoOptional, with return_date: where the return trip drops off, if not the first trip's pickup. Defaults to the first trip reversed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / bags / description
      Previous value: -"Large bags (suitcases; a pram or stroller counts as one). Goes into book_url. The quote lists vehicles by passengers only, so check the bags against the fleet in get_service_info: the Kia Carnival takes more when fewer people travel."New value: +"Large bags (suitcases; a pram or stroller counts as one). Goes into book_url. The quote lists vehicles by passengers, so check the bags against the fleet in get_service_info: the Kia Carnival takes more when fewer people travel. With pax and bags, the Transporter is left out when the group has more large bags than it takes (up to 8 for 9-11 people): two vehicles take them."
    • changedInput schema / properties / pax / description
      Previous value: -"Total passengers including children. With pax the quote lists only the vehicles that take the whole group, as the booking engine does: groups of 8 or more get the two-vehicle options and the VW Crafter (up to 11 passengers, one van for the whole group)."New value: +"Total passengers including children. With pax the quote lists only the vehicles that take the whole group, as the booking engine does: groups of 8 or more get the two-vehicle options and the 12-seater Transporter (up to 11 passengers, one vehicle for the whole group)."
    • changedInput schema / properties / vehicle / description
      Previous value: -"Chosen vehicle: sedan | carnival | carnival_rav4 | two_carnivals | crafter | crafter_trailer (sets book_url; book_urls has all)"New value: +"Chosen vehicle: sedan | carnival | carnival_rav4 | two_carnivals | transporter (sets book_url; book_urls has all)"
  2. Changed1 schema field changed
    • changedInput schema / properties / flight / description
      Previous value: -"Flight number, e.g. JQ430"New value: +"Flight number, e.g. JQ430 (goes into book_url). An airport pickup is only booked with the flight number they land on."
  3. Changed2 schema fields changed
    • changedInput schema / properties / bags / description
      Previous value: -"Large bags"New value: +"Large bags (suitcases; a pram or stroller counts as one). Goes into book_url. The quote lists vehicles by passengers only, so check the bags against the fleet in get_service_info: the Kia Carnival takes more when fewer people travel."
    • changedInput schema / properties / oversized / description
      Previous value: -"Oversized luggage (surfboards, golf clubs, prams)"New value: +"Surfboard, golf bag, bike box or similar (takes the space of three large bags, so the sedan drops out). Not for a pram or stroller: that is one large bag in bags, and it means the Carnival rather than the sedan."
  4. Changed2 schema fields changed
    • addedInput schema / properties / return_stops
      Added value: +{
      +  "description": "Optional, with return_date: stops on the way back, in order, up to 4, same rules as stops. Not copied from stops: leave out for no stops on the way back.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 4,
      +  "type": "array"
      +}
    • addedInput schema / properties / stops
      Added value: +{
      +  "description": "Optional: stops on the way (drop someone off, a shop, a second hotel), in order, up to 4. Each a street address (number and street, suburb) or a hotel or venue name with its suburb, never just a suburb. The booking form adds the detour through them, charged by the extra distance and the same for every vehicle. On a return these are the stops on the way there. Leave out for none.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 4,
      +  "type": "array"
      +}
  5. Changed2 schema fields changed
    • addedInput schema / properties / return_dropoff
      Added value: +{
      +  "description": "Optional, with return_date: where the return trip drops off, if not the first trip's pickup. Defaults to the first trip reversed.",
      +  "type": "string"
      +}
    • addedInput schema / properties / return_pickup
      Added value: +{
      +  "description": "Optional, with return_date: where the return trip picks up, if not the first trip's drop-off (e.g. a different hotel). Defaults to the first trip reversed.",
      +  "type": "string"
      +}
  6. Changed1 schema field changed
    • changedInput schema / properties / return_date / description
      Previous value: -"Return leg date YYYY-MM-DD, if a return"New value: +"Return leg date YYYY-MM-DD, if a return: adds return_totals_aud (the whole return trip per vehicle)"
  7. Changed2 schema fields changed
    • changedInput schema / properties / date / description
      Previous value: -"Travel date YYYY-MM-DD (goes into book_url)"New value: +"Travel date YYYY-MM-DD (goes into book_url; closures are checked)"
    • changedInput schema / properties / pax / description
      Previous value: -"Total passengers including children. With pax the quote lists only the vehicles that take the whole group, as the booking engine does: groups of 8 or more get the two-vehicle options and the VW Crafter (one van for 8-11)."New value: +"Total passengers including children. With pax the quote lists only the vehicles that take the whole group, as the booking engine does: groups of 8 or more get the two-vehicle options and the VW Crafter (up to 11 passengers, one van for the whole group)."
  8. Changed2 schema fields changed
    • changedInput schema / properties / pax / description
      Previous value: -"Total passengers including children"New value: +"Total passengers including children. With pax the quote lists only the vehicles that take the whole group, as the booking engine does: groups of 8 or more get the two-vehicle options and the VW Crafter (one van for 8-11)."
    • changedInput schema / properties / vehicle / description
      Previous value: -"Chosen vehicle: sedan | carnival | carnival_rav4 | two_carnivals (sets book_url; book_urls has all)"New value: +"Chosen vehicle: sedan | carnival | carnival_rav4 | two_carnivals | crafter | crafter_trailer (sets book_url; book_urls has all)"
  9. First observed

TDQS

A4.7/5.0
Behavior5/5

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

The annotations only declare readOnlyHint and openWorldHint; the description adds a great deal beyond them — GST/tolls included, no surge, price locked at booking, closure checks returning available:false with no prices, holiday surcharges itemised, return discount applied to the cheaper trip, and the fact that a stop-containing quote omits book_url. It also discloses output fields (fares_aud, totals_aud, return_totals_aud, book_url/book_urls, place_corrected, address_check) despite no output schema.

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 and the most important constraint are front-loaded, but the body is one very long, dense block of run-on sentences with repeated restatements (the return-total point is made twice, book_url explained at length). Much of it earns its place, yet it would be far more scannable broken into short labelled sections.

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

Completeness5/5

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

For a 17-parameter tool with no output schema, the description covers the return shape (which totals field applies to which trip), the failure mode (available:false plus closure message), surcharge reporting, and the booking-link contract. An agent has everything needed to call it and to report results correctly.

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?

Schema coverage is 100%, so the baseline is 3; the description earns above that by explaining cross-parameter behaviour the schema does not: return_pickup/return_dropoff each priced at their own fare with the discount off the cheaper trip, stops priced by extra distance and identical across vehicles, and date triggering closure checks before pricing. It does not, however, add much to the individually documented fields (pax, bags, seats, oversized).

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

Purpose5/5

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

Opens with a specific verb and resource: exact fixed prices for a transfer between two locations from the live booking engine. It states the pricing basis (per vehicle, AUD, GST and tolls included, locked, no surge) and names the sibling used instead when stops are involved (request_booking), so an agent can tell it apart from request_booking and check_availability.

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

Usage Guidelines5/5

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

Explicit routing rules: quote return_totals_aud for a return and never the one-way fare; book stop-inclusive quotes with request_booking because they have no book_url; pass date/time/passengers/luggage/flight here so the link carries them; ask the customer for a flight number for airport pickups. It also gives an explicit prohibition: never estimate a figure yourself when no fixed price exists.

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