Wedtide wedding seating

Seat wedding guests at tables with keep-apart rules; returns an editable plan and seat finder.

我該用這個嗎

品質與安全性

A
說明品質
100%
結構描述完整度
95%
命名品質
90%
汙染風險
100%
權限相符程度
100%
協定合規性
100%

根據工具定義與協定合規性的自動化分析。

上下文成本

~748Token(工具定義)
~2.3 KB典型回應大小
中等的注意力影響(128k 上下文的 0.58%)

這是每次將伺服器的工具載入模型上下文時所消耗的約略 token 數量。數量越高,可用於其他工作的注意力就越少。

安裝

一鍵安裝

將以下內容加入你的 `claude_desktop_config.json` 檔案:

{
  "mcpServers": {
    "seating": {
      "url": "https://wedtide.com/api/mcp"
    }
  }
}

遠端端點

https://wedtide.com/api/mcpstreamable-http

它能做什麼

工具清單

工具(2)

🟢 唯讀🟡 寫入🔴 刪除⚪ 未知
🟢create_seating_plan(guests, seats_per_table, rules, couple, setting)

Arrange a wedding guest list at tables and return a link that opens the plan in Wedtide. Use when the user shares a guest list (pasted names, a spreadsheet, CSV) and wants a seating chart or table assignments. Couples and families written on one line ("Ana & Luis", "The Smiths: John, Mary, Tim (kid)") are kept at the same table; rules keep named guests apart or together. Returns a short summary of who sits at each table and anything that could not be satisfied, plus two links: plan_url opens the full, editable plan in Wedtide (saved on the user's device; they can move people, view the room in 3D, print, export), and finder_url is a page guests open to type their name and see their seat. Nothing is stored on a server; the guest list is encoded in the link.

輸入結構描述

{
  "type": "object",
  "properties": {
    "guests": {
      "type": "string",
      "description": "The guest list as text. One party per line; \"&\", \"+\", \"and\" or commas join people who arrive together. A line ending in \":\" starts a group (\"Bride's family:\"). \"(kid)\" marks a child. A CSV or tab-separated sheet with a header row (name, party/household, group, age...) also works, e.g. exports from Zola, The Knot or Google Sheets."
    },
    "seats_per_table": {
      "type": "integer",
      "description": "Seats at each round table. Default 10.",
      "minimum": 2,
      "maximum": 30
    },
    "rules": {
      "type": "array",
      "description": "Requests about specific guests, by name as written in the list. \"apart\" keeps two guests at different tables (exes, feuding relatives); \"together\" seats them at the same table.",
      "items": {
        "type": "object",
        "properties": {
          "a": {
            "type": "string",
            "description": "A guest name."
          },
          "b": {
            "type": "string",
            "description": "Another guest name."
          },
          "kind": {
            "type": "string",
            "enum": [
              "apart",
              "together"
            ]
          }
        },
        "required": [
          "a",
          "b",
          "kind"
        ]
      }
    },
    "couple": {
      "type": "string",
      "description": "The couple's names, shown as the plan's title, e.g. \"Emma & James\"."
    },
    "setting": {
      "type": "string",
      "enum": [
        "ballroom",
        "vineyard",
        "garden",
        "beach"
      ],
      "description": "The look of the 3D room in Wedtide. Default ballroom."
    }
  },
  "required": [
    "guests"
  ]
}
🟢seating_tips(culture, guests)

Concise, practical wedding seating etiquette: head table or sweetheart table, where parents sit, divorced or feuding parents, kids tables, plus-ones, singles, and how many tables to plan. Use it when the user asks who should sit where or how to handle a delicate seating situation. Optional culture adds notes for some traditions; guests adds a table count.

輸入結構描述

{
  "type": "object",
  "properties": {
    "culture": {
      "type": "string",
      "description": "Optional tradition or region, e.g. \"american\", \"jewish\", \"latin american\", \"indian\", \"chinese\". Unknown values get the general guidance."
    },
    "guests": {
      "type": "integer",
      "description": "Optional number of guests, for a table count.",
      "minimum": 1
    }
  }
}

社群

為此伺服器評分

證據

近期觀測

已驗證未記錄版本2 個工具