TripWays

Get tour details

get_tour_details

Read-onlyIdempotent

Get the full details of one TripWays tour by bokun_id (the number in tripways.com/t/{id}): summary, itinerary stops, inclusions and exclusions, languages, cancellation policy, meeting point or pickup, from-price, rating, hero_image, url, and checkout_url. Live dates and group totals come from check_availability and get_price_quote.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`bokun_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`url`	No	The tour's TripWays page.
`error`	No	Present when ok is false. code: tour_not_found, destination_not_found, destination_ambiguous, or unpriced. message is written for the traveler.
`title`	No
`rating`	No
`reason`	No	Why checkout works the way it does, e.g. pickup_required.
`themes`	No
`summary`	No
`bokun_id`	No	Tour id; the number in tripways.com/t/{id}.
`guidance`	No
`itinerary`	No
`languages`	No
`activities`	No
`exclusions`	No
`from_price`	No	Lowest adult price.
`hero_image`	No	Main photo URL.
`inclusions`	No
`cancellation`	No	free, flexible, partial, or non_refundable.
`checkout_url`	No	TripWays checkout for this tour.
`destinations`	No
`hotel_pickup`	No
`duration_text`	No
`gttd_eligible`	No	Listed on Google Things to Do.
`duration_hours`	No
`bookable_natively`	No	True when checkout_url opens TripWays checkout; false when it opens the operator calendar.
`meeting_pickup_label`	No

Schema Changelog

Changes observed during successful MCP inspections.

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

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds meaningful behavior beyond that: this returns static catalog content (summary, itinerary, inclusions, cancellation policy, hero_image, checkout_url) while volatile data lives in the two named siblings. It doesn't address error behavior for a nonexistent id, which is the only notable gap.

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?

Two sentences, front-loaded with the action and the identifier source, then a short routing clause naming the alternatives. No filler and nothing redundant with the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with an output schema and full annotation coverage, this is complete: the agent knows what it gets, how to form the key, and which siblings cover the data this tool deliberately omits.

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 0%, so the description must carry the load, and it does: it translates bokun_id into 'the number in tripways.com/t/{id}', which tells the agent where to obtain the value. It doesn't restate the numeric-only pattern, but the URL decoding implies it clearly enough.

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 (fetch full details of one tour) and pins the identifier semantics to a concrete artifact ('the number in tripways.com/t/{id}'). It also enumerates the payload, so an agent can distinguish it from search_tours and the availability/quote siblings at a glance.

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 live dates and group totals to check_availability and get_price_quote, which is exactly the boundary an agent needs. It doesn't state a when-not condition for this tool itself (e.g., use search_tours first to find an id), so it falls just short of full when/when-not guidance.

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?