Skip to main content
Glama

TripFinder.ca

Compare tours side by side

compare_trips
Read-onlyIdempotent

Compare two to four tours on the same facts: price, duration, route, group size, age limits, comfort and activity level, flights, inclusions, meals, accommodation, transport, itinerary outline and next departures.

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": {
      "slugs": "<slugs>"
    },
    "name": "compare_trips"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugsYes
currencyNoCurrency for prices. CAD is the default; use USD for travellers in the United States.CAD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and purity are covered. The description adds the compared fact set but says nothing about behavior beyond that: no handling of invalid or unknown slugs, no statement about ordering of results, and no note that output mirrors the input slug order.

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?

A single front-loaded sentence with the verb, cardinality, and scope stated first, followed by the enumerated comparison fields. The long fact list is dense but each item earns its place by telling the agent what comes back.

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 only two parameters, no nested objects, and no output schema, the enumeration of compared facts effectively substitutes for describing return values. Minor gaps remain around failure modes for bad slugs and result ordering, but an agent has enough to call it correctly.

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 50%: currency is documented in the schema, while slugs carries only constraints (pattern, minItems 2, maxItems 4). The description restates the 2–4 bound but adds no meaning about slug format or about how slugs map to result ordering. Adequate, but not compensating for the undocumented parameter.

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?

Uses a specific verb ("Compare") on a specific resource (tours) and scopes it to "two to four tours on the same facts," then enumerates the compared attributes. This clearly separates it from the single-tour sibling get_trip and from search_trips without needing to name them.

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?

The "two to four tours" phrasing implies the appropriate scenario (side-by-side evaluation of a shortlist), but the description never states when to prefer this over calling get_trip multiple times, nor any exclusions or prerequisites. Usage is inferable rather than guided.

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