tripinned-mcp 1.0.15 → 1.0.17
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/dist/index.js +1 -1
- package/package.json +1 -1
package/dist/index.js
CHANGED
|
@@ -48,7 +48,7 @@ Tripinned trip planning rules:
|
|
|
48
48
|
- Each item belongs to exactly one day; do not split a single event across multiple days.
|
|
49
49
|
- When adding flight segments, group the full route (origin → stopover → destination) as one item if the user is just passing through.
|
|
50
50
|
- To show an item in the route map, set show_on_route to true. For place items, provide either lat/lng for a single location or locations for up to 10 ordered place stops. For flights, provide origin/destination IATA codes in from_place and to_place; no separate coordinates are needed. For non-flight transport, provide from_place/from_lat/from_lng and/or to_place/to_lat/to_lng.
|
|
51
|
-
- Hotel stays
|
|
51
|
+
- Hotel stays must use icon HOTEL with check-in in start_time, check-out in end_time, and end_day_offset for the check-out day. The API creates a check-in/check-out group with one shared groupId; add_item returns the check-in item and get_trip shows both items.
|
|
52
52
|
`.trim(),
|
|
53
53
|
});
|
|
54
54
|
// ── Trips ────────────────────────────────────────────────────────────────────
|