Jinko Hotel Booking MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find-placeA | Use this tool to convert a user's location query into standardized place information with coordinates. This is essential when you need latitude and longitude for hotel searches but only have a text description. The tool accepts city names, hotel names, landmarks, or other location identifiers and returns a list of matching places with their details and precise coordinates. |
| search-hotelsA | Search for available hotels based on location coordinates and booking requirements. This tool returns a paginated list of hotels with their key details including name, address, star rating, price range, and available room types. Each hotel includes summary information about amenities and available rates. The results are limited to 50 hotels per request. If more results are available, you can retrieve them using the load-more-hotels tool with the returned session_id. |
| load-more-hotelsA | Retrieve additional hotel results from a previous search using the session_id. This tool continues pagination from a previous search-hotels request, returning the next batch of hotels with the same format and details as the original search. The response format matches search-hotels and includes information about whether further pagination is possible. |
| get-hotel-detailsA | Retrieve comprehensive details about a specific hotel identified by its ID. This tool provides more extensive information than what's available in search results, including complete descriptions, all available room types, detailed rate information, cancellation policies, and full amenity lists. Use this tool when a user expresses interest in a specific hotel from search results to provide them with all available options and complete booking information. |
| book-hotelA | Initiate a hotel booking process for a specific hotel and rate option. IMPORTANT WORKFLOW:
The response includes a payment_link that must be prominently displayed to the user, along with booking details such as hotel name, check-in/out dates, and total price. |
| get-facilitiesA | IMPORTANT: ALWAYS USE THIS TOOL FIRST when a user mentions ANY specific hotel amenities or requirements. This tool must be called BEFORE search-hotels whenever the user mentions requirements like:
The tool returns facility IDs that MUST be used with the search-hotels tool's facilities parameter to properly filter hotels. Without using this tool first, searches will not correctly filter for user-requested amenities. Example workflow:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Hotel Facilities (en) | Hotel facilities translated to en |
| Hotel Facilities (es) | Hotel facilities translated to es |
| Hotel Facilities (it) | Hotel facilities translated to it |
| Hotel Facilities (he) | Hotel facilities translated to he |
| Hotel Facilities (ar) | Hotel facilities translated to ar |
| Hotel Facilities (de) | Hotel facilities translated to de |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose with no overlap: find-place converts location queries, get-facilities retrieves amenity IDs, search-hotels finds hotels, get-hotel-details provides full hotel info, load-more-hotels handles pagination, and book-hotel initiates bookings. The descriptions explicitly define their roles, preventing misselection.
All tool names follow a consistent verb_noun pattern with hyphens (e.g., find-place, get-facilities, search-hotels). This uniformity makes the set predictable and easy to understand, with no deviations in style or convention.
With 6 tools, the server is well-scoped for hotel booking, covering the full workflow from location search to booking. Each tool earns its place, providing essential steps without bloat or redundancy, typical for a focused domain like this.
The toolset offers complete coverage for hotel booking: location handling (find-place), amenity filtering (get-facilities), hotel search and pagination (search-hotels, load-more-hotels), detailed information (get-hotel-details), and booking initiation (book-hotel). No gaps exist, ensuring agents can handle the entire lifecycle without dead ends.