Fortrip
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FORTRIP_TOKEN | No | Optional CLI access token (fth_…), preferred over saved credentials. | |
| FORTRIP_API_URL | No | Optional API origin; defaults to https://fortrip.ai. HTTPS required except localhost development. | |
| XDG_CONFIG_HOME | No | Optional configuration root; otherwise ~/.config is used. Saved credentials are read from $XDG_CONFIG_HOME/fortrip/credentials.json. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_planning_guideA | Read before planning flexible dates, budget trips, split stays, multiple destinations or best-hotel comparisons. Explains what to ask, live-rate evidence and how to rank options. |
| search_hotelsA | Find hotels by query (name, brand or city), cityCode or near coordinates for checkIn/checkOut. Prices are indicative nightly floors in CNY (default) or USD: quote get_rates, not search prices. Facilities must match catalogue names. Narrow searches refused with 422. Use get_planning_guide for complex trips. |
| get_hotelA | Static catalogue facts for hotelId: address, contact, description, policies, check-in/out times, facilities and photos. includeRooms adds catalogue rooms. No live prices or availability. |
| get_ratesA | Live rooms and rate plans for 1–15 hotelIds and a stay of 1–15 nights. Specify rooms and adults per room; provide every child age. Prices in CNY (default) or USD. Returns roomId/ratePlanCode for create_booking and meal/cancellation terms. Defaults to 5 cheapest rooms per hotel. Takes about 15 seconds; query a few hotels per call. Use search_hotels first to find IDs, get_hotel for static policies/photos, and get_planning_guide for flexible trips. Use this tool to verify availability and quote live prices before booking. Requires Fortrip login; 429 errors include retry guidance. |
| create_bookingA | Create or resume a booking for a user-selected rate from get_rates. Provide guests and contact details. Returns amount, currency, accepted terms and a private paymentUrl. Show terms and ask for confirmation before sharing paymentUrl exactly. Nothing is charged until the user pays on Fortrip/Stripe. Same user and stay resumes the same order; paid stays return 409. Does not cancel or modify bookings. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct phase (planning guidance, hotel discovery, live rates, booking, static facts), and descriptions explicitly steer usage (e.g. 'quote get_rates, not search prices'). There is mild overlap between search_hotels, get_hotel and get_rates since all three surface hotel data, but the static/live/discovery boundaries are clearly drawn.
All five tools follow a clean verb_noun snake_case pattern (get_planning_guide, search_hotels, get_rates, create_booking, get_hotel). No mixed conventions or vague standalone verbs.
Five tools is a lean but sensible surface for a search-and-book flow, and each earns its place. It sits near the thin end for a booking domain, but nothing is redundant.
The search → rates → book path is covered, plus static facts and a planning guide. However there is no way to cancel, modify, or retrieve existing bookings/orders, and create_booking itself states it does not cancel or modify, leaving agents at a dead end for post-booking lifecycle operations.