Skip to main content
Glama

Shuttlely private charters

Price a Toronto trip

get_quote
Read-only

Instant per-vehicle price range (CAD, tax included) for Toronto routes, airport transfers or a custom route, from the public price book. Read-only: books nothing.

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": {
      "startDate": "<startDate>",
      "guests": "<guests>"
    },
    "name": "get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
bagsNoChecked suitcases and carry-ons; helps pick a vehicle with room for them
guestsYesGuests including children; 1-7 can price instantly
routesNoToronto route slugs from list_routes, in travel order. Use routes or customDays, not both.
languageNoLanguage of titles and emails
childAgesNoAges of the children among the guests; car seats are free
startDateYesFirst service day, YYYY-MM-DD, Toronto time; up to about 18 months ahead
customDaysNoA custom route from Toronto: one short line per day in the traveller's words. Always a written quote.
dropoffDateNoWith airportDropoff: the flight-home date if later than the standard drop-off
vehicleClassNoOptional; defaults to the smallest class that fits
airportPickupNoOptional airport pickup on the start date; touring starts the next morning
airportDropoffNoOptional airport drop-off, by default the morning after the last touring day
extraHoursPerDayNoExtra hours per touring day beyond the included 10

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description reinforces this with "Read-only: books nothing", which is the key behavioral reassurance for a pricing tool. It adds genuine context beyond annotations: prices are in CAD, tax included, sourced from the public price book, and some inputs (custom route, "other" zone) fall back to a written quote rather than an instant price.

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

Conciseness5/5

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

Two short sentences with no filler, front-loaded with the output and its currency, followed by the read-only guarantee. Every clause carries information an agent would not get from the name alone.

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?

For a 12-parameter tool with nested objects, the description covers what is returned and the key behavioral caveats, while the unusually rich schema handles parameter detail. It could say more about the instant-vs-written-quote boundary conditions and what a price range contains, but nothing essential to invocation is missing.

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 description coverage is 100%, so every parameter is already documented in detail, including the routes-vs-customDays exclusivity and the 1-7 guest instant-pricing limit. The description adds only the framing that prices are per-vehicle and tax-inclusive, which does not extend parameter meaning much beyond 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?

States a concrete verb-and-output ("Instant per-vehicle price range") with currency and tax basis, plus the scope (Toronto routes, airport transfers, custom route). An agent knows exactly what comes back. It does not name a sibling, but the "Instant" vs "Always a written quote" contrast in the schema makes the distinction from a manual-quote path visible.

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 is implied rather than stated: "Instant" signals this is the fast pricing path, and "books nothing" signals it is not the booking step. There is no explicit when-not guidance or named alternative (e.g. use request_quote when a written quote is needed), so the agent must infer routing from the contrast.

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