TourMind Hotel Booking

View saved version →

---
name: tourmind-hotel-booking
description: Search hotels, compare live rates across booking channels, inspect rooms, verify availability, submit bookings after user confirmation, and manage hotel orders through the TourMind hotel OAuth connection. Payment is conditional on the connected service and host policies. Use for hotel requests handled by this plugin; respect the user's chosen service and constraints.
license: MIT
metadata:
  author: TourMind
---

# TourMind hotel booking

Use the MCP connection alias **`tourmind-hotel`**, configured at **`https://mcp-booking.tourmind.com/mcp/oauth/toc`**. This Skill supports hotels only. It is self-contained and does not require another Skill or a local credential file. Follow the user's explicit constraints and the host's higher-priority instructions. Respond in the user's current language; translate the visible labels and templates naturally.

## Connection and actual tool contract

OAuth authorization and credentials belong to the host-managed connection. Direct the user to the host's connection/sign-in flow when authorization is needed. Never ask for passwords, email verification codes, OAuth codes, access/refresh tokens, API keys or legacy hotel keys in chat. Never read credential files, secret headers, environment variables, another connection, or conversation history to obtain them. Do not use direct HTTP, curl, an old endpoint, or an API-key fallback for hotel operations.

**The new OAuth endpoint's authenticated `tools/list` has not been verified during packaging.** Earlier hotel services exposed the names below; these are capability-matching hints, not proof that this endpoint exposes the same tools, arguments, results or permissions:

| Needed operation | Earlier tool name, only if actually exposed |
|---|---|
| Resolve location | `search_location` |
| Search hotels | `search_hotels` |
| Hotel details/images | `get_hotel_detail` |
| Live rooms/rates | `query_room_rates`, `batch_query_room_rates` |
| Final availability/price verification | `check_room_availability` |
| Create a booking | `create_booking` |
| Query/cancel an order | `query_booking`, `cancel_booking` |
| Payment initiation | `pay_order`, only when actually authorized and permitted |

Before a workflow call, use the hotel tools and schemas actually exposed by `tourmind-hotel`. Match capabilities using their real descriptions. Send only accepted fields, exact documented enums, and required user-provided values. Do not guess an alternate tool name or manufacture a request. If a capability/schema is missing, state what is unavailable and request only the needed user input or service documentation. In particular, if a tool still requires a model-supplied legacy credential, stop that operation and explain that the OAuth integration must bind the account server-side; never collect or fabricate the credential.

Read [references/parameter_guide.md](references/parameter_guide.md) when constructing searches, interpreting returned fields, or handling orders. Its earlier field mappings apply only when confirmed by the connected service. Do not run update, maintenance or unrelated tools as a prerequisite to the user's hotel request.

On an authentication rejection, stop the affected operation and guide reconnection through OAuth. On a permission rejection, explain the missing permission without assuming that the credential is expired. Do not claim to have cleared or changed connection settings. A failed connection never authorizes trying another account or endpoint. Do not test authorization by creating or cancelling an order or initiating payment.

## Search and compare

For a request limited to static hotel details or images, use an exposed static capability without requiring stay dates when its schema permits. Dates and occupancy become necessary before dated search, live rates or booking; ask only for the missing values.

1. Complete location, check-in and check-out before hotel search. Resolve relative dates in the 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 2 — file references are metadata, not package contents.