@gojinko/plugin 2.1.1 → 2.3.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -9,13 +9,14 @@ You have access to Jinko MCP tools for flight discovery. Pick the right one base
|
|
|
9
9
|
|
|
10
10
|
## Tool Selection
|
|
11
11
|
|
|
12
|
-
| User intent
|
|
13
|
-
|
|
14
|
-
| Nothing in mind — wants inspiration
|
|
15
|
-
| Route known, flexible on dates — wants the full price-per-date list
|
|
16
|
-
| Route known, flexible on dates — wants a short curated spread of date options ("when should I fly?") | `find_dates`
|
|
17
|
-
| Route +
|
|
18
|
-
| Route + exact dates,
|
|
12
|
+
| User intent | Tool to use |
|
|
13
|
+
| ---------------------------------------------------------------------------------------------------- | ------------------------------------------- |
|
|
14
|
+
| Nothing in mind — wants inspiration | `find_destination` |
|
|
15
|
+
| Route known, flexible on dates — wants the full price-per-date list | `flight_calendar` |
|
|
16
|
+
| Route known, flexible on dates — wants a short curated spread of date options ("when should I fly?") | `find_dates` |
|
|
17
|
+
| Route + **fixed** date — wants the cheapest fares for that exact day (cached) | `lowest_fare` |
|
|
18
|
+
| Route + exact dates, wants live pricing + bookable token | `flight_search` (see the `book-trip` skill) |
|
|
19
|
+
| Route + exact dates, **wants to track price over time** | `price_monitoring` |
|
|
19
20
|
|
|
20
21
|
> `find_flight` (cached search by route + dates) still exists for backwards compatibility but is no longer recommended — `flight_search` returns live prices and a `trip_item_token` in a single step.
|
|
21
22
|
|
|
@@ -24,10 +25,12 @@ You have access to Jinko MCP tools for flight discovery. Pick the right one base
|
|
|
24
25
|
Discover destinations from origin airports. Returns destinations sorted by cheapest flight.
|
|
25
26
|
|
|
26
27
|
**Required params:**
|
|
28
|
+
|
|
27
29
|
- `origins`: array of IATA codes (include all nearby airports, e.g. `["JFK", "LGA", "EWR"]` for NYC)
|
|
28
30
|
- `trip_type`: `"oneway"` or `"roundtrip"`
|
|
29
31
|
|
|
30
32
|
**Optional params:**
|
|
33
|
+
|
|
31
34
|
- `destinations`: filter to specific destinations
|
|
32
35
|
- `departure_dates` or `departure_date_ranges`: when to depart
|
|
33
36
|
- `return_dates` or `return_date_ranges`: when to return (roundtrip)
|
|
@@ -44,6 +47,7 @@ Discover destinations from origin airports. Returns destinations sorted by cheap
|
|
|
44
47
|
Show cheapest prices across a date range for a specific route. Great for "what's the cheapest day to fly?"
|
|
45
48
|
|
|
46
49
|
**Required params:**
|
|
50
|
+
|
|
47
51
|
- `origin`: IATA code (e.g. `"PAR"`)
|
|
48
52
|
- `destination`: IATA code (e.g. `"NYC"`)
|
|
49
53
|
- `trip_type`: `"oneway"` or `"roundtrip"`
|
|
@@ -51,6 +55,7 @@ Show cheapest prices across a date range for a specific route. Great for "what's
|
|
|
51
55
|
- `departure_date_end`: end of range (YYYY-MM-DD)
|
|
52
56
|
|
|
53
57
|
**Optional params:**
|
|
58
|
+
|
|
54
59
|
- `return_date_start`, `return_date_end`: return range (roundtrip)
|
|
55
60
|
- `stay_days`: exact stay duration
|
|
56
61
|
- `direct_only`, `cabin_class`, `currency`
|
|
@@ -69,6 +74,18 @@ Answers "when should I fly?" — takes the **same params as `flight_calendar`**
|
|
|
69
74
|
|
|
70
75
|
**flight_calendar vs find_dates:** use `flight_calendar` for the full price-per-date grid; use `find_dates` when you want a short, spread-out shortlist of the best date options to fly.
|
|
71
76
|
|
|
77
|
+
## lowest_fare
|
|
78
|
+
|
|
79
|
+
Cheapest fares for a **fixed** route + date — takes the **same params as `flight_calendar`** but, for one specific departure date (one-way, or `+ return_dates` for round-trip), returns up to **10 itineraries sorted cheapest-first**. **Cache-only.** It's the fixed-date counterpart of `flight_calendar`.
|
|
80
|
+
|
|
81
|
+
**Required params:** `origins`, `destinations`, `trip_type`, `departure_dates` (a single fixed date).
|
|
82
|
+
|
|
83
|
+
**Optional params:** `return_dates` (round-trip), `direct_only`, `cabin_class`, `currency`.
|
|
84
|
+
|
|
85
|
+
**Response:** up to 10 full itineraries (same shape as `flight_calendar`), cheapest-first.
|
|
86
|
+
|
|
87
|
+
**When to use which:** `flight_calendar`/`find_dates` for flexible dates; **`lowest_fare` when the date is fixed** and you just want the cheapest options that day.
|
|
88
|
+
|
|
72
89
|
## find_flight (legacy — prefer flight_search)
|
|
73
90
|
|
|
74
91
|
Cached flight search by route + dates. Still callable for backwards compatibility with older ChatGPT App versions, but not recommended for new integrations. Use `flight_search` (in the `book-trip` skill) for the same inputs plus live pricing + a bookable `trip_item_token` in one step.
|
|
@@ -78,17 +95,20 @@ Cached flight search by route + dates. Still callable for backwards compatibilit
|
|
|
78
95
|
Track the price of a specific route + exact dates over time. **Cache-only** — never triggers a live call. Designed for scheduled polling (cron / scheduled job) so you can act on a price drop.
|
|
79
96
|
|
|
80
97
|
**Required params:**
|
|
98
|
+
|
|
81
99
|
- `origin`: IATA code (e.g. `"PAR"`)
|
|
82
100
|
- `destination`: IATA code (e.g. `"NYC"`)
|
|
83
101
|
- `departure_date`: YYYY-MM-DD
|
|
84
102
|
- `return_date`: YYYY-MM-DD (omit for one-way)
|
|
85
103
|
|
|
86
104
|
**Optional filters** (use the SAME set between polls — switching filters mid-poll means you're monitoring a different route, not the same one cheaper):
|
|
105
|
+
|
|
87
106
|
- `direct_only`, `cabin_class`, `max_price`
|
|
88
107
|
- `include_carriers` / `exclude_carriers` (IATA 2-letter codes)
|
|
89
108
|
- `currency`, `locale`
|
|
90
109
|
|
|
91
110
|
**Response:**
|
|
111
|
+
|
|
92
112
|
- `status: "ok"` with a `flight` block (cheapest cached itinerary matching the filters), OR
|
|
93
113
|
- `status: "stale"` when the cache had no matching itinerary — retry later. **Do NOT silently fall back to `flight_search`** on stale; that's a different intent. Only call `flight_search` if the user is ready to book RIGHT NOW.
|
|
94
114
|
|