Skip to main content
Glama

TripFinder.ca

Get tour details

get_trip
Read-onlyIdempotent

Full public facts for one tour: day-by-day itinerary, inclusions and exclusions, meals, accommodation, transport, group size, age limits, international flight status, promotions, and upcoming departure dates with per-person prices and availability.

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": {
      "slug": "<slug>"
    },
    "name": "get_trip"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
currencyNoCurrency for prices. CAD is the default; use USD for travellers in the United States.CAD
departuresToNoOnly list departures starting on or before this date.
departuresFromNoOnly list departures starting on or after this date.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive behavior, and closed-world scope. The description adds useful response-content context by saying it returns public facts, itinerary details, prices, and availability, but it does not describe error behavior for missing slugs or how date filters affect returned departures.

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

Conciseness4/5

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

The definition is one front-loaded sentence with a dense but purposeful inventory of returned facts. The long field list is information-dense rather than redundant, though it could be easier to scan if split into response categories.

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?

With no output schema, the description helpfully enumerates what a successful call returns: itinerary, inclusions, meals, accommodation, transport, group size, age limits, flight status, promotions, and upcoming departures. Combined with annotations and mostly described schema parameters, it is nearly complete, though it omits parameter-filter behavior and invalid-slug handling.

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 high at 75%, and descriptions already explain currency and the departuresFrom/departuresTo filters. The prose description adds no parameter-level meaning beyond naming upcoming departure dates; it does not clarify how the slug, currency, or date filters interact with returned prices and availability.

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 phrase 'Full public facts for one tour' clearly identifies retrieval of detailed data for a single tour and distinguishes it from list/compare siblings by emphasizing 'one tour' and 'full public facts.' It lacks an explicit verb like 'retrieve,' but the resource and scope are specific.

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

Usage Guidelines2/5

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

The description provides no explicit when-to-use or when-not-to-use guidance, and it does not name alternatives such as search_trips or compare_trips. Usage is only implied by 'for one tour,' leaving the agent to infer that this follows a search rather than using a list or comparison tool.

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