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

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

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.

Changed1 schema field changedOct 29, 2026

changedOutput schema / properties / tours / items / properties / from_price / description

Previous value: -"Lowest adult price."New value: +"What one adult pays: the tour page's From price, the same price Google shows."

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.5/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent and closed-world behavior. The description adds that results are ranked and that filters are optional ('any filters you already know'), which guides partial-query usage. It does not disclose result-set sizing or the effect of the limit cap, but with annotations carrying the safety profile this is close to complete.

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?

Three sentences, front-loaded with purpose and usage before the field list. The return-field enumeration is somewhat wasted because an output schema exists, but it does not obscure the actionable guidance.

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 10-parameter, read-only search tool with an output schema, the description covers purpose, filter semantics and sibling routing. Only behavior around the limit cap and result ranking/ordering is unstated, which is a small residual 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?

Schema description coverage is only 30%, so the description does real work: it enumerates query, destination, price range in USD, duration in hours, activity, theme and cancellation policy, confirming all are optional refinements. Only 'limit' is left unexplained, which is a minor gap given its documented default and maximum in the schema.

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 and resource ('Search the TripWays catalog of bookable tours, day trips, and activities worldwide') and scopes it to catalog discovery rather than live availability. An agent can distinguish it from check_availability and get_price_quote without reading either schema.

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

Usage Guidelines5/5

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

Explicitly describes two modes: free-text query plus optional known filters. It also names the exact conditions that route elsewhere — live dates, remaining seats, group totals go to check_availability and get_price_quote. This is a clear when-to-use / when-not-to-use split.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?