Relaunch decision checker
toolfound_relaunch_decisionChoose between a relaunch, a regular update, or more preparation from the size of the change and launch evidence you provide. Use it when you have already launched and are unsure whether to relaunch, post a regular update, or prepare more first. Returns one of three verdicts (plan a relaunch, publish a regular update, prepare before promoting) with the reasons and next actions, based only on the answers given. Returns an evidence-bounded result and the canonical web tool URL.
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": {
"change": "<change>",
"audienceChanged": "<audienceChanged>",
"listingCurrent": "<listingCurrent>",
"evidence": "<evidence>",
"measurementReady": "<measurementReady>"
},
"name": "toolfound_relaunch_decision"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| change | Yes | Size of the biggest change since your last launch: small is incremental improvements, major is a new workflow or a new audience, direction is a different product direction. | |
| evidence | Yes | What you can show for the update: strong is a working release plus specific proof such as a demo or numbers, release is a working release only, none means it is not released yet. | |
| listingCurrent | Yes | yes if your public listing, screenshots and facts already match the product as it is today. | |
| audienceChanged | Yes | yes if the people you are targeting are different from the last launch. | |
| measurementReady | Yes | yes if tracking, support ownership and a review date are already in place for the announcement. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | ||
| data | No | ||
| links | Yes | ||
| errors | No | ||
| summary | Yes | ||
| sections | Yes | ||
| canonical_result_url | Yes |