Loyalist Reservations

com.eatloyalist由 eatloyalist.com 發布官方發布者v1.0.0更新於 Oct 27, 2026

Book tables at restaurants on the Loyalist network. No login; read availability, then book.

已驗證Streamable HTTP可網頁執行位置與生活效率與工作流

概覽

AI 產生的概覽

讓助理在 Loyalist 網路的餐廳中尋找可訂餐廳、查詢空位、預訂座位、查看訂位狀態並加入候補名單。

可以做什麼
  • 尋找可預訂的餐廳,可依報名表單或其他條件縮小範圍
  • 依日期與人數查詢某家餐廳的可訂時段,回傳時段 ID 與餐廳當地時間
  • 使用空位結果中的時段 ID 預訂座位
  • 讀取同一憑證所做的訂位,確認是否成功
  • 為客人想要的時間申請加入候補名單,但不保留座位
適用情境
適合讓助理在 Loyalist 網路上查詢餐廳空位並完成訂位,或在理想時段有空位時收到通知。適用於餐廳、日期、時間與人數都已確認的對話式用餐安排。
執行需求
遠端 MCP 端點 agent.eatloyalist.com,使用 streamable HTTP;未宣告登入、套件、環境變數或標頭。查詢空位需要餐廳當地日期與用餐人數。
安裝前請注意
預訂會佔用真實餐廳的真實座位,且沒有取消工具,誤訂須由客人透過餐廳撤銷;呼叫前應先與本人確認餐廳、日期、時間與人數,切勿試探性預訂。pending 狀態表示尚未回覆,並非失敗。候補申請不是訂位,也不會保留座位。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Loyalist Reservations,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/com.eatloyalist%2Frestaurant-reservations/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "loyalist-reservations": {
      "type": "http",
      "url": "https://agent.eatloyalist.com/mcp"
    }
  }
}

工具

5

find_venues

Find venues

Restaurants bookable through this network, and what each one's system supports. Returns every venue that has opted in, across restaurant groups. Two optional filters narrow it, never widen it: `signup_form_id` to one website's venues when you found an Orion signup embed on a restaurant's page, and `venue_id` to a single venue when you already have its loyalist-venue-id (off a page's markup or a ReserveAction entry point) and want just that one rather than listing them all and matching yourself. Neither can reach a venue that has not opted in. A venue with `bookable: false` has no reservation system connected and will return no availability.

輸入參數venue_idsignup_form_id

get_availability

Check availability

Bookable times at one venue, on one date, for one party size. `date` is the venue's own local calendar date, `YYYY-MM-DD`. Each slot carries a `slot_id` to pass to book and a `starts_at` that is a full venue-local datetime, so a service running past midnight is unambiguous without you having to infer the day. An empty `slots` list means nothing is open on those terms, not that the venue is closed. Try a different time, party size or date before telling someone it is full.

輸入參數date必填venue_id必填party_size必填

book

Book a table

Book a table. This takes a real table at a real restaurant. Pass a `slot_id` from get_availability. Confirm the venue, date, time and party size with the person before calling this, and do not call it speculatively: there is no cancel tool, so a booking made by mistake has to be undone by the guest phoning the restaurant. Calling it twice with identical arguments is safe and returns the same reservation rather than taking a second table. Changing the slot or the guest makes it a different booking, so re-read availability rather than editing the arguments to "retry". `phone` is optional here but required by some venues; omitting it can come back as `guest_field_required`. `note` reaches the restaurant as the reservation's note. `source` is where you found this venue: if the restaurant's own website told you a value to pass (in its markup or llms.txt), send it here so the restaurant can see its own site drove the booking. Leave it out if you did not arrive through one. `reservation_id` is for your own use, to read the booking back with get_reservation. It is not a confirmation number the venue knows, so do not read it out to the guest: tell them the restaurant, date, time and party size instead.

輸入參數noteemail必填phonesourceslot_id必填last_name必填first_name必填

get_reservation

Look up a reservation

Read one booking this credential made back from the venue. Use it to confirm a booking landed. A `status` of `pending` means the venue has not answered yet, not that it failed; treat anything you do not recognise as non-terminal rather than reporting a failure.

輸入參數reservation_id必填

join_waitlist

Join the waitlist

Ask to be told if a table opens at a time the guest actually wants. This is not a reservation and never becomes one by itself. The venue contacts the guest if something frees up, so say that plainly rather than implying a table is held. Offer it whenever the guest cannot get a time that suits them, which is far more often than a venue being completely full: someone who wants 7:30 and is offered 5:00 or 9:45 may well prefer to wait for 7:30. An empty get_availability is only the most obvious case. Try other times, party sizes and dates first, then ask whether they would rather wait than take a time that does not work. Record what they wanted in `time_range`, not the time you found. `date` is the venue's own local calendar date, `YYYY-MM-DD`. `time_range` is required and is the window in the guest's words, like "7:00 PM - 9:00 PM" or "7:00 PM"; ask the guest for it rather than guessing, because the venue works the list by when people wanted to come. The email address is where the confirmation goes, so it must be the guest's own. Not every venue accepts these. One that does not refuses with a message saying so, which is an answer, not an error to retry. There is no reference number to give the guest, so the response is the only record either of you gets. Confirm it back to them by the restaurant, date and time. Mention the confirmation email only when `confirmation_sent` is true. When it is false the request is still on the venue's list, the note simply did not go out, so say they are on the list and that no email is coming rather than promising one.

輸入參數date必填email必填notesphonevenue_id必填last_name必填first_name必填party_size必填time_range必填

版本歷史

1
  1. v1.0.0最新Oct 14, 2026

評分

已滿足適用檢查項的 83%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分

    請宣告包含 README 的 GitHub 儲存庫,或在 OAuth 受保護資源後設資料中提供 resource_documentation。

  • 授權條款不適用

    託管服務按其提供方的條款使用,因此這裡不要求授權條款。此檢查項不計入百分比。