Skip to main content
Glama

TripFinder.ca

Request a quote or booking

request_quote
Destructive

Start a booking: send the traveller's chosen trip(s), preferred departure date(s) and contact details to a TripFinder travel advisor, who replies within one business day with the confirmed price and availability and completes the booking with the traveller. Creates a real request read by people, so it is for when the traveller has asked for a quote, given their own contact details and agreed to be contacted. Does not take payment or guarantee a place.

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": {
      "tripSlugs": "<tripSlugs>",
      "name": "<name>",
      "adults": "<adults>",
      "consentToContact": "<consentToContact>"
    },
    "name": "request_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe traveller's full name.
emailNoThe traveller's email. Email or phone is required.
notesNoAnything the advisor should know: flexibility, budget, mobility, dietary needs, questions.
phoneNoThe traveller's phone number. Email or phone is required.
adultsYesNumber of adult travellers.
currencyNoCurrency for prices. CAD is the default; use USD for travellers in the United States.CAD
tripSlugsYesSlugs of the trip(s) the traveller wants quoted, from search_trips or get_trip.
childrenAgesNoAge of each child travelling, if any.
departureCityNoHome city/airport, for flight advice.
departureDatesNoPreferred departure start dates from get_trip. Leave empty if the traveller is flexible.
roomPreferenceNo
consentToContactYesTrue when the traveller has explicitly agreed that TripFinder may contact them about this request using the details provided. The request is not sent otherwise.
contactPreferenceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare non-read-only, destructive, open-world and non-idempotent behavior, so the description's job is to add context — and it does: the request is read by real people, replied to within one business day, takes no payment and guarantees no place. The notable gap is that it never warns that repeated calls create multiple separate requests, which matters given idempotentHint=false and a human on the other end.

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 sentences, no filler, and the core action and turnaround are front-loaded before the guardrails. Every clause — human-read request, precondition, no payment, no guaranteed place — carries distinct information.

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 13-parameter mutation tool with no output schema and human-mediated follow-up, the description covers purpose, timing of the response, and outcome limits well. It is only incomplete about what the agent should tell the traveller after submitting, and about avoiding duplicate submissions.

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?

With schema coverage at 85%, the schema already documents most fields, so the baseline is 3. The description goes slightly beyond it by grouping the meaningful inputs (trips, preferred dates, contact details) and by reframing consentToContact as a substantive precondition ('given their own contact details and agreed to be contacted') rather than a mere boolean flag.

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 gives a specific verb and resource — sending chosen trips, departure dates and contact details to a TripFinder travel advisor to start a booking — plus the reply channel and turnaround (one business day). It clearly separates this from read-only discovery tools, but does not distinguish itself from the similarly named 'contact_advisor' sibling, which an agent could plausibly confuse with 'submit a quote request'.

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

Usage Guidelines4/5

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

It states explicit preconditions — the traveller must have asked for a quote, supplied their own contact details, and agreed to be contacted — and gives clear exclusions: no payment taken, no place guaranteed. It stops short of pointing to an alternative for cases where those preconditions don't hold (e.g. general enquiries), so it falls just under the top mark.

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