TripWays

Get a price quote

get_price_quote

Read-onlyIdempotent

Get the live total for a TripWays tour on one date and start time for a traveler mix, priced from the operator's booking calendar. A quote does not hold seats or charge anything. Optional extras and promo codes are not included. When the tour's rates cannot price that mix, the result is unpriced.

Input Schema

TableJSON Schema

Name	Required	Description
`date`	Yes
`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

TableJSON Schema

Name	Required	Description
`ok`	Yes
`date`	No
`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
`currency`	No
`from_price`	No
`quote_kind`	No
`rate_title`	No
`start_time`	No
`checkout_url`	No	Checkout preset to this date, time, and travelers.
`package_total`	No	Total for the whole group, before optional extras and promo codes.
`promo_applied`	No
`min_participants`	No
`travelers_priced`	No	Traveler counts the total covers.
`bookable_natively`	No
`includes_required_extras`	No
`optional_extras_excluded`	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.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: no seat hold, no charge, extras/promos excluded, and the 'unpriced' failure mode when rates can't price a mix.

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?

Four tight sentences, front-loaded with the core action and scope, followed by the non-obvious constraints (no hold/no charge, exclusions, unpriced outcome). No filler, though the final sentence could be folded in.

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 shape needn't be described. For a read-only pricing tool with a nested traveler object, the description covers scope, side effects and the failure case adequately; only the id/time-id parameter ambiguity is left unaddressed.

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

Parameters3/5

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

Schema description coverage is only 40%, so the description should compensate more than it does. It ties date, start time and traveler mix together meaningfully, but says nothing about bokun_id or the start_time vs start_time_id precedence, leaving those to the schema alone.

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 ('Get the live total for a TripWays tour') plus the exact scoping inputs (date, start time, traveler mix) and the pricing source (operator's booking calendar). This is clearly distinguishable from check_availability and search_tours 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 context for use: a quote is a pre-booking price check that does not hold seats or charge, and it excludes extras and promo codes. It stops short of explicitly routing to sibling tools (e.g. 'use check_availability to hold seats'), so it is strong but not exhaustive.

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?