TripWays

Search tours

search_tours

Read-onlyIdempotent

Search the TripWays catalog of bookable tours, day trips, and activities worldwide. Pass a natural-language query plus any filters you already know: destination, price range in USD, duration in hours, activity, theme, or cancellation policy. Returns ranked tours with bokun_id, title, from-price, duration, destinations, rating, cancellation policy, hero_image, the TripWays page (url), and checkout_url. For live dates, remaining seats, or a group total, use check_availability and get_price_quote.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`query`	Yes	Natural-language search, e.g. 'family food tour in Rome under $100'.
`theme`	No
`activity`	No	Activity facet, e.g. food, hiking, snorkeling.
`price_max`	No
`price_min`	No
`destination`	No	Place name (city, region, country, or well-known area/landmark). Resolved against TripWays destinations; a landmark that is not a destination is added to the search text.
`cancellation`	No
`duration_hours_max`	No
`duration_hours_min`	No

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`note`	No	Why the list is empty or how the destination was read.
`error`	No	Present when ok is false. code: tour_not_found, destination_not_found, destination_ambiguous, or unpriced. message is written for the traveler.
`tours`	No	Ranked tours; empty when nothing matched (see note).
`guidance`	No
`did_you_mean`	No	Candidate destinations when the place name matched more than one location.
`destination_resolved`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 2, 2026

addedOutput schema / properties / did_you_mean

Added value: +{
+  "description": "Candidate destinations when the place name matched more than one location.",
+  "type": "array"
+}

addedOutput schema / properties / error

Added value: +{
+  "description": "Present when ok is false. code: tour_not_found, destination_not_found, destination_ambiguous, or unpriced. message is written for the traveler.",
+  "properties": {
+    "code": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedSep 29, 2026

TDQS

A4.2/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 the safety profile is covered structurally. The description adds that results are 'ranked' and enumerates returned fields, which is useful behavioral context, but it adds nothing about pagination limits or scoring behavior beyond the limit cap in 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, each earning its place: what it searches, how to call it, what it returns, and the sibling handoff. The core purpose is front-loaded in the first clause with no filler.

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?

An output schema exists, so return values need not be explained, though the description redundantly enumerates them. Given the 10-parameter surface and low schema coverage, the description covers the meaningful filter semantics and routing; only the untouched limit/duration-range params leave a minor gap.

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?

With only 30% schema description coverage across 10 params, the description compensates well by naming the filter families (destination, price range in USD, duration in hours, activity, theme, cancellation policy) and clarifying the USD unit, which the schema's price_min/price_max do not state. It does not explain limit or the duration_min/max pairing explicitly, so it is not exhaustive.

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 (Search) and resource (TripWays catalog of bookable tours, day trips, activities), and explicitly contrasts scope with siblings by routing live availability/pricing to check_availability and get_price_quote. An agent can distinguish it from get_tour_details and get_destination_info without opening any 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?

Gives clear usage context ('Pass a natural-language query plus any filters you already know') and names two alternatives with the conditions that select them (live dates, remaining seats, group total). It stops short of an explicit when-not-to-use statement for search itself, but the routing is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TripWays tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?