Skip to main content
Glama

TripFinder.ca

List destinations, operators and styles

list_catalog_options
Read-onlyIdempotent

The countries, regions, tour operators (with trip counts) and travel styles currently in the catalog, plus the valid activity levels, comfort levels and sort orders for search_trips.

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_catalog_options"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds only the notion of a current-catalog snapshot and that operators come with trip counts; it says nothing about size, caching or freshness of that snapshot. Useful but marginal beyond the annotations.

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?

A single tightly packed sentence that front-loads the concrete catalog entities and ends with the actionable tie-in to search_trips. No filler, no restatement of the title alone.

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 carries the burden of describing return content, and it does enumerate the returned categories including operator trip counts. It could say slightly more about the shape of the response (e.g. grouped lists) but is adequate for a parameterless lookup.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. Schema coverage is 100% as well, leaving no gap to compensate for.

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 description enumerates the specific catalog resources returned (countries, regions, operators with trip counts, travel styles) plus the valid filter values for search_trips. That is concrete and distinguishable from siblings like get_trip or list_guides, though the verb is only implied by the name/title rather than stated in the sentence.

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?

By naming search_trips and tying the returned activity levels, comfort levels and sort orders to it, the description makes the intended use case clear: fetch valid filter values before searching. It stops short of an explicit when-not-to-use statement or naming other alternatives.

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