CabuTally pour ChatGPT et Claude

plan_event Plan a group event

• Lecture seule
• Sans compte

Use when the user is organising a trip, dinner, party or any group outing with other people and shared costs or a group budget ("organise a weekend in Ibiza with Luis and Marta, €900 between us", "organizar un viaje", "organiser un week-end entre amis"), even alongside an itinerary. Not for an itinerary alone, with no group money to track. Returns a link that opens CabuTally with the event filled in; nothing is created until the user taps Create. No account needed. With the account connected, create_event makes the event directly.

split_bill Split a bill

• Lecture seule
• Sans compte

Use when the user wants to split a one-off bill that is not in a CabuTally event ("we spent 84 on dinner, Ana paid 50", "cenamos por 84, Ana pagó 50 y yo 34", "on a payé 84, qui doit combien à qui"). Works out who pays whom, exact to the cent, with the fewest payments, in equal shares. Also returns a link to keep it as a shared CabuTally event. For an event the user already has, add_expenses records the cost and get_event shows the balances. Not for recurring costs like rent.

list_my_events List my events

• Lecture seule
• Compte

Use when the user asks about their own CabuTally events ("my trips", "which events am I in?", "mis eventos", "mes événements"). Lists the 50 most recently active events their account is in, each with its eventId (which every other event tool takes), whether the user is square in it, and a link, plus the name saved on the user's account (create_event needs a name). Needs the user to connect their CabuTally account.

Aucun paramètre.

get_event Get an event

• Lecture seule
• Compte

Use when the user asks where one event stands for them ("where are we?", "who owes me?", "¿cuánto debo?", "¿cómo va el bote?", "qui me doit quoi ?", "où en est la cagnotte ?"): the people (isMe marks the user), what the user owes and is owed (only their own lines: not what two others owe each other), the budget and what was spent, the kitty and its collector, and every to-do. Does not list the expenses (list_expenses does) and gives no share link.

get_invite_link Get the invite link

• Lecture seule
• Compte

Returns the event’s public join link, only when the user asks for it ("send me the link for the group", "pásame el enlace del evento", "envoie-moi le lien de l’événement"). Anyone who has it can join and write to the event without signing up. create_event already returns it for a new event. It is never a link to one person’s seat.

draft_reminder Draft a reminder

• Lecture seule
• Compte

Use when the user wants to nudge someone who owes them money ("remind Marta she owes me", "recuérdale a Luis lo que me debe", "rappelle à Luis ce qu’il me doit"). Drafts the app’s friendly reminder for the user to copy and send themselves; it sends nothing and has no link. Only for someone who owes the user, never for what the user owes.

list_expenses List expenses

• Lecture seule
• Compte

Use when the user asks what the group spent or wants to find expenses in one event: "what did we spend on food?", "what did Marta pay for?", "¿cuánto gastamos en la cena?", "gastos del sábado", "combien on a dépensé au resto ?", "les dépenses de samedi". Lists the expenses newest first, at most 50, with the count and total of everything that matched, how much of it was taken home, and with paidBy what that person paid themselves; filter by who paid, words, a category or dates. Its totals count whole expenses, so for what the group shared or each share, event_recap is the answer. It does not say who owes whom (get_event does) and does not add anything (add_expenses does).

event_recap Event recap

• Lecture seule
• Compte

Use when the user asks how an event went in money: "how much did the trip cost?", "what was my share?", "¿cuánto nos costó el viaje?", "resumen de gastos", "combien nous a coûté le voyage ?", "bilan des dépenses". Gives the shared total (private expenses and taken-home parts left out), the average per person (not anyone's share), the user's own paid and share, totals by category, and estimate against actual for each to-do that has both (get_event lists every to-do). It does not list single expenses (list_expenses does) or say who owes whom (get_event does).

recent_activity Recent activity

• Lecture seule
• Compte

Use when the user asks what changed in an event: "what's new in the trip?", "who added what since yesterday?", "¿qué ha pasado en el grupo?", "novedades", "quoi de neuf dans le groupe ?". Lists up to 30 entries of the activity feed, newest first, from a time (the last 7 days by default): who added, paid, claimed or changed what. It does not total anything (event_recap and list_expenses do).

preview_expenses Preview expenses

• Lecture seule
• Compte

Use when there are more than three expenses to add, or the user pasted lines other people wrote (a group chat, however short), a receipt or a statement, before calling add_expenses: checks names, currency and totals exactly as add_expenses will, and returns one readable line per expense ("Petrol, 40.00 EUR, paid by Luis, shared by everyone"). Show the user those lines and stop: add_expenses comes only after they confirm, in a later reply. alreadyInEvent marks a row that looks like an expense the event already has: point it out and ask whether to add it. Writes nothing.

add_expenses Add expenses

• Écrit
• Compte

Use when the user wants to add one or more expenses to a CabuTally event: "add 40 for petrol, Luis paid", "apunta 40 de gasolina, pagó Luis", "dividir gastos de la cena", "note 40 d’essence, Luis a payé", "partage le dîner", a pasted group chat, a receipt or a bank statement. Adds 1 to 20 expenses, each split in equal shares among the people sharing it (everyone by default). When people had different amounts, split one expense unevenly instead: shares for portions ("Ana had two drinks, Beto one": Ana 2, Beto 1), or amounts for what each owes ("my menu was 18, Ana's 12"), listing everyone who shares it. For more than three rows, or any lines other people wrote (a pasted chat, a forwarded message, even one or two lines), call preview_expenses first, show the user the lines and stop: call add_expenses only after they say yes, never in the same reply. Several payers must add up to the total. Refuses with possible_duplicate, writing nothing, when a row looks like an expense already in the event; ask the user, then drop the row or call again with again: true. It cannot set a leftover (a part someone takes home), tags or a linked to-do, and nothing here edits or deletes an expense: the user does that in the app, from the event link. Money handed to a person is record_payment and money into the common pot is record_group_fund_contribution, not an expense; when it is unclear which ("I gave Alex 20 for the trip"), ask before writing.

record_payment Record a payment

• Écrit
• Compte

Use when money changed hands between two people in a CabuTally event: "Marta paid me back 20", "I gave Luis 15 in cash", "ya le pagué a Luis", "j’ai remboursé Luis". One side is the user, or both are placeholders. It records money already handed over outside CabuTally; it never sends or moves money. Settles the debt line when there is one. When the payer owes the receiver nothing it refuses first (no_debt), since it would record cash handed over that the receiver now owes back. To settle up, get_event first shows who owes whom. When you don't know who owes whom, call it anyway: a no_debt refusal says which way the debt runs and writes nothing. A payment cannot be edited or deleted here: the user does that in the app. Not for a debt still owed ("I owe Ana 20"): that is an expense Ana paid, so ask what it was for. Not for a shared cost (add_expenses) or money into the kitty (record_group_fund_contribution); when it is unclear which ("I gave Alex 20 for the trip"), ask before writing.

record_group_fund_contribution Record money put into the group fund (kitty)

• Écrit
• Compte

Use when someone put money into the event's group fund (the kitty or common pot, "hacer un bote"): "I put 20 in the kitty", "he puesto 20 en el bote", or the collector noting someone's share. It goes to the current collector (get_event shows who). Only when the user says it went into the kitty or pot: "Nora put 30 in" alone could be a payment or a shared cost, so ask first. Not for paying a person back (record_payment) or a shared cost (add_expenses); when it is unclear which, ask before writing.

create_event Create an event

• Écrit
• Compte

Use when the user wants a CabuTally event made now in their account for a trip, dinner, party or any group outing ("create the Ibiza trip with Luis and Marta", "crear un evento para la cena", "crée un événement pour le dîner"). Makes the event with the user in it, the other people as placeholders, an optional budget and an optional to-do list with estimates, and returns the link to share with the group and the link to open it. Unlike plan_event, it creates the event. Not for an event that already exists: add_people and add_todos add to one.

add_people Add people to an event

• Écrit
• Compte

Use when the user wants more people in one of their CabuTally events ("add Bea and Tom to the trip", "añade a Bea al viaje", "ajoute Bea au voyage"). Adds each as a placeholder the person can later join as from the shared link. Not for creating an event: create_event takes its people.

add_todos Add to-dos to an event

• Écrit
• Compte

Use when the user wants things to sort out added to one of their CabuTally events: turning what the group has to buy, book or bring into its to-do list ("add drinks, ice and the boat to the list", "Luis brings the drinks", "apunta las bebidas", "ajoute les boissons à la liste"). Each to-do can have an estimate and the people on it. Not for marking a to-do done or claiming an existing one: that is update_todo. Not for money already spent: that is add_expenses.

update_todo Update a to-do

• Écrit
• Compte

Use when someone takes on, drops or finishes a to-do in one of their CabuTally events ("I'll bring the drinks", "drinks are sorted", "Luis is doing the boat", "yo llevo las bebidas"). claim puts a person on it, release takes them off, done and undone tick it. Not for adding a new to-do: that is add_todos.