Request database restore
databaseRestoreRequestAsk a person at Tofu by email to put one owned app’s running managed database back to one of its daily backups — Ask for a restore on the Database page. A restore puts the WHOLE database back to that moment, losing everything saved since — new rows, changes, anyone who signed up — and the app cannot reach its database while it runs. Requires confirmed: true, representing the human’s agreement to this exact projectId and backup with that data loss and downtime; without the literal nothing is sent. The human gets a confirmation email (replying to it cancels); nothing in the database changes until the person at Tofu restores it and emails the human. The backup is backupId or date (UTC: that day’s newest complete backup); note goes to that person. The answer is a report with a human-readable message; outcome is requested, refused (nothing was sent) or not_sent (nobody got it, so nothing will happen; asking again later is safe). It returns no credential.
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": {
"projectId": "<projectId>",
"confirmed": "<confirmed>"
},
"name": "databaseRestoreRequest"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | ||
| note | No | ||
| backupId | No | ||
| confirmed | Yes | ||
| projectId | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| at | Yes | ||
| code | Yes | ||
| backup | Yes | ||
| message | Yes | ||
| outcome | Yes | ||
| receipt | Yes | ||
| projectId | Yes | ||
| requestId | Yes |