TripWays

Get a booking link

get_booking_link

Read-onlyIdempotent

Get the TripWays checkout link for a tour, optionally preset to a date, start time, rate, and traveler mix. The traveler pays on tripways.com; this tool does not hold seats or take payment. bookable_natively and reason say whether the link opens TripWays checkout or the operator's calendar, and whether a hotel pickup must be chosen at checkout.

Input Schema

Name	Required	Description
`date`	No
`rate_id`	No	Option to preselect: the rate_id get_price_quote priced or one from its rate_options. Omit for the option a quote would price.
`bokun_id`	Yes
`travelers`	No	Simple ages; mapped to Bokun pricing categories.
`start_time`	No	HH:MM if start_time_id unknown.
`start_time_id`	No

Output Schema

Name	Required	Description
`ok`	Yes
`error`	No	Present when ok is false. code: tour_not_found, destination_not_found, destination_ambiguous, or unpriced. message is written for the traveler.
`reason`	No
`bokun_id`	No
`spots_left`	No
`start_time`	No
`checkout_url`	No	Open in the browser to pay on tripways.com.
`min_participants`	No
`bookable_natively`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

addedInput schema / properties / rate_id / description

Added value: +"Option to preselect: the rate_id get_price_quote priced or one from its rate_options. Omit for the option a quote would price."

Changed1 schema field changedOct 2, 2026

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

Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, yet the description adds real context: the link does not hold inventory or process payment, and the returned bookable_natively and reason indicate whether checkout happens on TripWays or the operator's calendar and whether a hotel pickup must be selected. That is exactly the side-effect clarity an agent needs before handing a link to a user.

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 dense sentences, front-loaded with the core action, then the payment/inventory disclaimer, then the return-field semantics. No filler and nothing repeated from the annotations.

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 covers return values and the description still explains bookable_natively and reason helpfully; the nested travelers object is noted as mapping to Bokun pricing categories. Minor gaps remain: bokun_id is never explained as the tour identifier, and link expiry/validity is unmentioned, which matters for a link-generation tool.

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 coverage is only 50%, but the description compensates by explaining the optional preset set (date, start time, rate, traveler mix) and by defining rate_id's relationship to get_price_quote's rate_options. It does not clarify bokun_id's meaning nor the start_time vs start_time_id precedence beyond what the schema text says.

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?

Names a specific verb and resource (get the TripWays checkout link for a tour) and enumerates the preset dimensions (date, start time, rate, traveler mix). It is clearly differentiated from siblings like get_price_quote and check_availability, which price and check rather than produce a purchasable link.

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?

The rate_id parameter text ties the tool to get_price_quote ('the rate_id get_price_quote priced or one from its rate_options'), which implies the quote-then-link workflow. It also states the traveler pays on tripways.com and the tool does not hold seats or take payment, but it never explicitly says when not to use it or that availability should be confirmed first.

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?