Skip to main content
Glama

TripFinder.ca

Ask a travel advisor

contact_advisor
Destructive

Send a general enquiry to a TripFinder travel advisor when the traveller has not settled on a specific trip, wants a custom recommendation, or has a question the catalog cannot answer. An advisor replies within one business day. Creates a real message read by people, so it is for when the traveller has asked to reach an advisor, given their own contact details and agreed to be contacted. request_quote is the better fit once a specific trip is chosen.

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": {
      "message": "<message>",
      "name": "<name>",
      "consentToContact": "<consentToContact>"
    },
    "name": "contact_advisor"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe traveller's full name.
emailNoThe traveller's email. Email or phone is required.
phoneNoThe traveller's phone number. Email or phone is required.
adultsNoNumber of adult travellers.
timingNoWhen they hope to travel, e.g. "September 2027, about two weeks".
messageYesWhat the traveller is looking for or wants to ask, in their words, with any useful context from the conversation.
currencyNo
childrenAgesNoAge of each child travelling, if any.
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.4/5.0
Behavior4/5

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

Adds real context beyond the annotations: the message is read by people, a reply takes up to one business day, and sending is gated on explicit consent. That meaningfully explains why destructiveHint=true and openWorldHint=true. The gap is that idempotentHint=false is never addressed — there is no warning that a repeat call sends a second real enquiry and cannot be recalled.

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?

Four sentences, each doing distinct work: purpose and trigger, service-level expectation, the human-review/consent constraint, and the sibling handoff. Front-loaded and free of repetition.

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 10-parameter write tool with no output schema, the description covers what an agent most needs: purpose, exclusions, consent gate, and response timing. It stops short of describing what the caller gets back on success or how to avoid duplicate submissions, which matters for a non-idempotent message-sending tool.

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 80%, so the parameters are largely self-documenting and baseline 3 applies. The description adds intent for the message field ('in their words, with any useful context from the conversation') and frames consent as a precondition, but says nothing about currency, contactPreference, adults, childrenAges, or timing, so it does not fully compensate for the remaining coverage gap.

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?

States a specific verb and resource ('Send a general enquiry to a TripFinder travel advisor') plus the conditions that make it the right call (no specific trip chosen, wants a custom recommendation, catalog can't answer). It explicitly names the sibling that takes over once a trip is chosen, so an agent can separate it from request_quote without opening either schema.

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?

Gives both when-to-use and when-not-to-use, names the alternative ('request_quote is the better fit once a specific trip is chosen'), and states prerequisites the traveller must satisfy before calling (asked for an advisor, supplied their own contact details, agreed to be contacted). Nothing is left to inference.

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