Compare two releases
compare_releasesEvery route, screen and page seen in both releases, with count, p50, p95 and error rate in each, sorted by the extra time per minute release b spends against a: what got slower or faster. Also what appears in only one of them. Take release names from list_releases or get_tracing_health; package@version+build works too, and a version alone is every build of it.
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": {
"a": "<a>",
"b": "<b>"
},
"name": "compare_releases"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| a | Yes | The earlier release | |
| b | Yes | The later release | |
| op | No | Only this op, like http.server or ui.load | |
| to | No | An ISO time, or how long ago (default now) | |
| from | No | An ISO time, or how long ago: 30m, 24h, 7d | |
| range | No | Window: 1h, 24h, 7d, 14d, 30d or 90d (default 24h). Ignored when from is given. | |
| source | No | backend (servers), frontend (app and web), or all (default) | |
| release | No | Only this release: 2.0.77+185, 2.0.77 (every build) or package@2.0.77+185 | |
| service | No | Only this service, like house-ai-api or the app's bundle id | |
| environment | No | Like production. Default: production when the app has it, else its busiest non-development one. 'all' for every environment. |