Cut the Cake

Release notes

Shape an event by talking: after the host signs in and chooses what to share, the plugin can change an event's details, wording, look, cover photo and features, add guests, report totals, and draft a message. It cannot send, delete, or publish without the host's own press. 1.1.1 corrects four tool annotations to match behavior: update_event_draft is destructive (it overwrites an event's details, wording and settings); publish_event is destructive (it makes a guest page public); check_ready_to_publish is not read-only (it stores a one-use publish code for its card); list_guests is not read-only (reading names makes the connection's later writes ask first). Every tool sets readOnlyHint, destructiveHint and openWorldHint explicitly. 1.1.2 asks for no password and no street address: the assistant can name a venue and its wifi network, and the host adds the address and the wifi password on Cut the Cake. Where publishing needs a plan the host doesn't have, the plugin says so and links nowhere. 1.1.3 takes the street address of the host's own event again, as an optional address on start_event_invitation and update_event_draft, so the invitation can show a map and directions; guests see it by the same rules as an address typed on Cut the Cake. An address sent as the place's name is saved as the address, and moving a published event's address is put to the host first, like its date and time. 1.1.3 also adds use_chat_image_as_cover: a picture the host put in the conversation becomes the event's cover, passed as a file parameter (openai/fileParams). It is fetched only from ChatGPT's file host, checked by its bytes and stored like a cover the host uploads on Cut the Cake, and it replaces the cover, so it is declared destructive and open-world. 1.1.3 also adds set_guest_answer: an answer the host was told somewhere else, recorded on the guest list with who is coming, their dishes, and an email address or phone number the host gives. It needs the host's "See who's coming, by name" switch, every call is put to the host before it saves, the guest is not told, and it never changes an address the guest answered or signed in with, a number the guest agreed to texts at, or a guest's note. 1.1.3 also draws the host's own sections on the invitation card, under the description as guests see them; they reach the card in the result's _meta, and no output schema changed. Every card now sets openai/widgetDescription, saying what it shows and which buttons it carries. get_event_draft also returns the next steps Cut the Cake's own Overview suggests for the event, in its order, each saying whether a tool here can do it; counts appear in them only where the host allowed the plugin to see how many are coming. The ready card's send button says how many invitations it sends where counts are allowed. A passage of wording that Custom wording governs is no longer saved while Custom wording is off, where guests would never see it: the plugin says so and saves it only when the same change turns Custom wording on, which it asks the host first. get_event_draft says where guests read each passage. The potluck's sign-up sheet (its items added or changed, never removed), its What to bring note and Ask for specific dishes, and the closing times of the potluck, nametags, song requests and song votes can now be set. get_event_draft returns a link to each of the event's pages on Cut the Cake (every tab it shows, Design, its settings and the guests' invitation), and get_event_summary counts what guests have made on the features that are on: photos, booth shots, guestbook notes, song requests and potluck sign-ups. 1.1.3 also adds add_co_host: the host's own assistant, behind a switch of its own that starts off, adds a co-host by the address the host gives, after putting that exact address and what a co-host sees to the host; Cut the Cake emails the new co-host. It never removes a co-host or reads back an address, and a co-host's own assistant cannot use it. It is declared not destructive (it only adds) and open-world (it emails a person). get_event_draft now lists every feature the product has, on or off, with a link to each one's settings on Cut the Cake, and Awards, the gift exchange and Insights can be switched on and off, with Awards' and the exchange's own settings; nominees, results, the draw and pairs stay on Cut the Cake. 1.1.3 also lets add_guests take the columns Cut the Cake's own guest-list import takes: a phone number, the later arrival, how many people the invitation allows, and an answer the host already has with their city and who is coming. Each entry is checked by the import's own rules and refused for the same reasons, the rest saving; when any entry carries an answer, its people or a phone number, the first call saves nothing and returns one line of counts for the host to agree to. It never changes a household already on the list, never saves a guest's note, and never says a phone number back. It is no longer declared idempotent (an entry with no address added twice is two households) and is now open-world (on a published event an answer it records changes the counts guests see). 1.1.3 also adds add_songs: songs the host names go onto the event's song requests, each looked up in the same iTunes search as Cut the Cake's Songs tab and saved only when one version is plainly it; where several versions could be meant, a picker card shows them with their artwork and an Apple Music link, and the host's press saves the one they choose. It follows the event's rules, refuses explicit tracks where the host hides them, reports a song already there, and never removes one. It is declared not destructive (it only adds) and open-world (it searches a public catalog, and guests see a published event's playlist). 1.1.3 also adds set_awards: the host's assistant names, renames and orders the event's awards, and chooses which potluck categories a dish award draws from, saved through the same database function as Cut the Cake's Awards tab and under its rules. It never removes an award; one the list leaves out is kept. It is declared destructive (a rename or a new order overwrites what the host set) and open-world (guests see a published event's awards). 1.1.3 also rewrites every tool's description to state only what the tool does, takes and returns, with nothing addressed to the model; a change that waits for the host's yes is described as behavior (the first call saves nothing and returns the change and a code, and the same call with that code saves it), and what applies to one call is said in its result. A picture ChatGPT hands over from its Azure file storage can now become the cover. Cards with nothing to draw show one line instead of an empty frame. get_event_summary counts households and answers as the Guests tab does and people as the Overview does. A change that waits for the host's yes is now named by change_id, an id of the form chg_ and sixteen characters that only Cut the Cake's server can make, bound to the connection, the event and the exact change, which the same call sends back to save it; the earlier confirm_change and confirm_live_change are still accepted. An address that can't be placed on a map is saved as written and the result says so, with the address exactly as saved. add_guests' summary names what will be left out or not used before the host agrees. add_songs holds a song whose title is already on the playlist in another version for the host to pick. Every card declares openai/widgetCSP and openai/widgetDomain beside its MCP Apps CSP. Tool descriptions no longer describe the confirmation steps at all; each pending change's result says them. A song named by its artist is added when that artist's version is found, saying other versions already on the playlist. get_event_summary's totals are counted in the database and reach the plugin as counts alone. A picture is fetched from one exact Azure storage account, never a pattern of them. A change recorded through set_guest_answer never queues a text to the guest. 1.1.3 also adds search_help: a question about Cut the Cake itself, such as what it offers, is answered from its published help center, the same search as the help center's own, with a link to each article. It needs no sign-in and reads no event, guest or account, so it is declared read-only, not destructive, idempotent and closed-world. list_event_drafts also says how many more events the host can edit that are not shared with this connection, as a count and never which, with a link to the page where the host shares them. get_event_draft and list_event_drafts say who the signed-in person is on each event: its host, a co-host (and who hosts it), a coordinator of its venue (on the venue's own event, or one handed to an outside host, where guests' contact details are masked) or event staff; a refusal that turns on that role says it. 1.1.3 also adds create_event: for a signed-in host, the assistant makes the draft in the host's account itself, the same draft the start link's Keep this invitation makes, shares it with the connection and draws it; the same details again return that draft. It publishes and sends nothing, so it is declared not read-only, not destructive (additive), closed-world (a private draft) and not idempotent. start_event_invitation is unchanged, and its result now says the event is made when the person presses Keep this invitation. A street address is now put to the host before it is saved on a draft too, not only on a published event, by update_event_draft and create_event alike; a place's name alone still saves at once. A picture ChatGPT generates in the chat can become the cover through use_chat_image_as_cover, as an attached one can. start_event_invitation's result says when this connection already holds a draft kept from an earlier link under the same title. A cover the assistant sets now brings the photo's colors when the host had chosen none, or was wearing the old photo's, as Cut the Cake's Design room does; colors the host chose, or asked for in the same request, are kept, and the result says the photo's are available. The next steps Cut the Cake's Overview suggests for an event now come with check_ready_to_publish, get_event_summary and update_event_draft's results too, not only get_event_draft's. set_guest_answer can also rename a household on the guest list, answered or not, put to the host first like its other changes; a name is never blank or one letter. The approval page now asks three things: which events (all of them, new ones included, or up to ten the host picks), whether the assistant may see who is coming by name, and whether it may add co-hosts, the last two off by default; editing the events it is given is what connecting is for. The host changes those answers later under Assistants on their account page, on the web or in the app, with no new connection. Connecting the same assistant again replaces its earlier connection, an account holds at most ten, and a tool refused because the host left something off links to that connection's own settings.

Declared in the saved package. Remote tools may change independently.