Skip to main content
Glama

TripFinder.ca

List travel guides

list_guides
Read-onlyIdempotent

TripFinder's sourced editorial guides: operator comparisons (e.g. G Adventures vs Intrepid), destination comparisons, what a tour price includes, travelling solo, choosing pace and difficulty. Returns each guide's short answer; use get_guide for the full text.

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

Input Schema

NameRequiredDescriptionDefault
queryNoOptional keywords to filter guides, e.g. "solo" or "vietnam".

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 readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new behavior: results are truncated to each guide's short answer, with get_guide as the path to full text. It omits result volume/pagination, which keeps it from a 5.

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?

Two sentences, no filler, with the resource identity front-loaded and the escalation rule last. The topic enumeration is dense but each item helps the agent decide whether a user question is in scope, so it earns its space.

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 one-optional-param, non-destructive read with no output schema, the definition covers what it returns (short answers), what it does not (full text), and what content exists. Only the absence of result-count/pagination expectations leaves a small gap.

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?

The single optional parameter is fully documented in the schema (maxLength 100 plus an example of "solo" or "vietnam"), so schema coverage is 100%. The description never mentions filtering or the query argument, adding no meaning beyond the schema — baseline 3 applies.

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 concrete verb+resource (list TripFinder's editorial guides) and immediately enumerates the covered topics (operator comparisons, price inclusions, solo travel, pace/difficulty), so an agent can match a user question to it. It also distinguishes itself from get_guide by noting it returns only the short answer.

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?

Explicitly routes the agent: this tool gives the short answer, get_guide gives the full text — a clear when-to-use-which rule. It does not say anything about when not to use it (e.g. vs search_trips or list_catalog_options), so it falls short of full alternative coverage.

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