Read uptime checks
siteChecksRead whether one owned app is answering its visitors. Every 5 minutes Tofu requests a live app’s home page at its public address, the way a visitor would, and keeps nothing it sends back. Two failed checks in a row open an outage and email the owner once; two good checks in a row close it and, after a “down” email, send one “answering again” email. emailsEnabled is the owner’s switch for those emails. openIncident and recentIncidents are the outages, each with whether the owner was emailed. last_check_failed is one failed check, not an outage yet; unavailable means this Tofu keeps no checks, so nothing here is a reading; an uptime window’s percent is null when it had no check. message is the recorded human-readable explanation of the check state. This read reports Tofu’s recorded visitor-check observations, not an application-level diagnosis. It writes nothing, and another account’s app answers not found.
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>"
},
"name": "siteChecks"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| projectId | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| state | Yes | ||
| uptime | Yes | ||
| address | Yes | ||
| message | Yes | ||
| available | Yes | ||
| lastCheck | Yes | ||
| projectId | Yes | ||
| openIncident | Yes | ||
| emailsEnabled | Yes | ||
| retentionDays | Yes | ||
| recentIncidents | Yes | ||
| checkEveryMinutes | Yes |