The MCP tools
The Bonafide MCP server exposes exactly two read-only tools.
bonafide_query Stable
Entity-aware natural-language query. The server resolves the hotel, brand, or destination you name in task, fetches matching documents across collections in parallel, scores them by relevance, and returns ranked results.
Arguments
| Argument | Type | Description |
|---|---|---|
task required | string | The natural-language question. Include the hotel or brand name for best entity resolution — e.g. "What is the check-in time at YOUR_HOTEL_NAME?" |
max_documents optional | integer | Maximum results to return. Default 10. Use 5–10 for focused answers, 20+ for broad research. |
min_relevance_score optional | number | Floor on the relevance score, 0.0–1.0. Use 0.5 for broad recall, 0.7+ for high-confidence matches only. Omit to return all scored results. |
response_format optional | enum | "text" (human-readable, with citations) or "json" (machine-readable). Default "json". Use "text" when the result is shown directly to a user. |
bonafide_search_documents Stable
Structured browse/filter over the knowledge base. Use this for discovery (“show me all spa-related Q&A”) rather than asking a question.
Arguments
| Argument | Type | Description |
|---|---|---|
query optional | string | Free-text filter, e.g. "spa treatments", "pet policy". |
type optional | enum | One of source_document, qa_pair, prompt_template, derived_data, official_link. |
category optional | string | Industry category: Hospitality (hotels/resorts), CarRental, or DMO (tourism boards). For hotels and resorts, use Hospitality. |
limit optional | integer | Page size, 1–100. Default 10. |
offset optional | integer | Number of documents to skip for pagination. Default 0. |
Last updated on