preview_proposal
Prepares a family proposal for review without sending it: recomputes the scenario's figures, returns the exact card text the family will see, and asks for explicit confirmation before sending.
Instructions
Prepares a proposal to the family without sending it: the first of two steps. Pass the scenario exactly as you evaluated it (a new goal is kind goal with name and targetDate), the title (at most 80 characters, one line), the short question (at most 300) and your verdict; for the next version of your own proposal that came back (status revising), also its proposalId (leave out the title to keep it). The title, the question, the reason and a new goal's name carry no digits, % or currency signs (a refused one is invalid_param naming it): name it without numbers, not even spelled out — 'a new phone', not 'iPhone 15'; 'the family car', not a model number; the server prints every number on the card. In the verdict, risk is the evaluation's or one step more cautious, never lighter (a refused risk gives params.computed), recommended is one of the evaluation's alternatives or null, and the reason is at most 200 characters. An evaluation whose risk is unknown cannot be proposed: tell the user what data is missing instead. The server weighs the scenario again and answers card.text, the card exactly as the family will get it in Telegram (in the family language); evaluation and baseCurrency, the exact figures behind it, recomputed now: the card rounds amounts to whole units and months to one decimal; a difference within that rounding is not a change. Shares are shown to one decimal too. If the exact figures differ from what you told the user, say so. Also voters (who will be asked to vote; your own vote counts as agree), acceptedAtOnce (true: you are the only voter, so it is accepted at once on sending), a draftId valid for 30 minutes and nextStep. Nothing is sent or stored. Show the user card.text and ask for an explicit yes; then send it with propose_to_family, or revise_proposal for a proposalId. Any change means a new preview.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"scenario": "<scenario>",
"question": "<question>",
"verdict": "<verdict>"
},
"name": "preview_proposal"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| title | No | The proposal's title as the user agreed to it, one line, no digits, % or currency signs: name it without numbers, not even spelled out — 'a new phone', not 'iPhone 15'; 'the family car', not a model number; the server prints every number on the card | |
| verdict | Yes | ||
| question | Yes | The short question put to the family, as the user agreed to it, no digits, % or currency signs: name it without numbers, not even spelled out — 'a new phone', not 'iPhone 15'; 'the family car', not a model number; the server prints every number on the card | |
| scenario | Yes | ||
| proposalId | No | Only for the next version of your own proposal that came back (status revising): its id, from list_proposals |