Voyscout Price History

Where it sits in the directory's order

What can be seen from outside, weighed as the directory publishes.

Where it answers

• https://voyscout.com/mcpstreamable-http

The tools it lists (5, as of 3 days ago)

The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.

• list_destinations

  List every destination with a published price series, with how many days each rail was actually measured and the calendar span those measurements fall in. A destination can have several rails (e.g. flights and packages), each with its OWN measured days and span: history depth is a property of the rail, not of the destination, so when you report it, name the rail or give each one. Historical observations only.

• price_history

  Price series for one destination: measured span, stats, a downsampled sample of points and any regime breaks. Historical observations only, never a live quote or a recommendation.

• current_vs_history

  Stats for one destination (min, median, and what share of the TRACKED DAYS were dearer than the last measurement) without the sample points. Percentages are over observed days, not over the calendar span. Descriptive only: it does not say whether to buy.

• find_opportunities

  Rank every published rail by how its LAST measurement compares with its own tracked history, so a caller can ask 'where is it unusually cheap right now?' in one call instead of one call per destination. Each row is ONE rail, so a destination with several rails can appear once per rail with different numbers: name the rail when you cite a row. Percentages are over observed days, not the calendar span. `latest_cheaper_than_pct_of_days` is the same number as `cheaper_than_pct` under a name that states its direction (higher = cheaper than more of the tracked days). `stale_rails` says how many of t

• compare_destinations

  Put 2-8 named destinations side by side on the same snapshot, each with the stats current_vs_history reports (last measurement, median, min, share of TRACKED DAYS that were dearer). Numbers are for the WHOLE party, not per person, and percentages are over observed days rather than the calendar span. Rows come back in the order you asked for - it does not rank, and gives no verdict; use find_opportunities to rank. A destination that yields no row is returned under `excluded` with the reason.