Get check history
get_check_historyRead one check's history as one row per calendar day, oldest day first: the date, how many runs were recorded (run_count), the mean response time in milliseconds (average_duration_ms, null for heartbeat, domain and SSL checks and for days with no measurement) and how many incidents started that day (incident_count). It's the summary to use for trends over weeks or months; it has no individual runs or percentiles. days is 7, 14, 30, 90 or 365 and defaults to 30; asking for more than the plan's limits.history_days returns quota_exceeded. An unknown check id returns not_found. time_zone (an IANA name) sets where each day starts and ends; the default is UTC, and the response names its zone along with the window's start_at and end_at.
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": {
"id": "<id>"
},
"name": "get_check_history"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Check id (check_…). | |
| days | No | Days of history, up to the plan's limit. Defaults to 30, or the plan's limit when shorter. | |
| time_zone | No | IANA time zone for days and timestamps, such as America/Chicago. Defaults to UTC. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| days | Yes | ||
| end_at | Yes | ||
| start_at | Yes | ||
| time_zone | Yes | ||
| retention_days | Yes |