Skip to main content
Glama

TripFinder.ca

Search tours

search_trips
Read-onlyIdempotent

Search TripFinder's catalog of multi-day guided group tours from operators including G Adventures, Intrepid, Exodus, Trafalgar, Collette and Exoticca. Filter by destination, dates, budget, activity level, comfort level and travel style. Returns 10 trips per page with from-prices, next departures and canonical URLs. Use get_trip for full details of a result.

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": "search_trips"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
sortNoResult order. Default is recommended.
queryNoFree-text search, e.g. "hiking in Peru", "Japan food tour in October", "safari under 5000". Understands destinations, months, styles and budgets.
dateToNoLatest acceptable end date. Use with dateFrom.
monthsNoDeparture months, 1–12. Ignored when dateFrom/dateTo are given.
currencyNoCurrency for prices. CAD is the default; use USD for travellers in the United States.CAD
dateFromNoEarliest acceptable start date. Use with dateTo; the trip must start on/after this and end on/before dateTo. Window is limited to 120 days.
dealsOnlyNoOnly trips with a current promotion.
operatorsNoLimit to these tour operators.
destinationNoA country (e.g. "Vietnam") or region (Africa, Asia, Europe, North America, Central America, South America, Middle East, Oceania, Antarctica, Arctic).
travelStyleNoA travel style from list_catalog_options, e.g. "Trekking & Hiking".
activityLevelNo
comfortLevelsNoService level, from basic (simple, budget) to luxury.
maxPricePerPersonNoMaximum from-price per person, in the requested currency.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: fixed page size of 10, and that results carry from-prices, next departures and canonical URLs. It omits any mention of the 120-day date window or result-count limits, which are left to the schema.

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?

Three sentences, front-loaded with the resource and operator scope, then filters, then return shape, then the sibling hand-off. No filler and nothing redundant.

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 14-parameter tool with no output schema, the description usefully characterizes the return payload and page size. Minor gaps remain: it never says that calling with no filters yields the default recommended listing, nor does it surface the 120-day date-window constraint that can silently invalidate a query.

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 coverage is 86%, so parameter meaning is largely already documented in structured fields. The description's list of filter dimensions (destination, dates, budget, activity level, comfort level, travel style) restates the schema rather than adding syntax or constraint detail, though the pointer to list_catalog_options for travelStyle values adds a little.

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 ("Search TripFinder's catalog of multi-day guided group tours") and scopes it with the operator list and the filter dimensions. It also explicitly separates itself from the sibling get_trip, so an agent can route between search and detail retrieval 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 Guidelines4/5

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

The final sentence gives a clear routing rule: use get_trip for full details of a result, and the travelStyle parameter points to list_catalog_options for valid values. It stops short of distinguishing search from compare_trips or explaining what to do when a search returns nothing, but the primary when-to-use context is explicit.

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