Preview notification routing
preview_notification_routingDry-run the organisation's notification routing: given a hypothetical notification (kind + severity, optionally cluster, source, application and reference), report which destinations it would reach, which routes matched or suppressed it and why, and whether the home channel fallback would be used. Nothing is sent. Use this to verify routing before and after changing routes. When you are confined to a project, another project's cluster or application answers not found, like a missing one, a source_id that a route would withhold from you (list_notification_routes says which) answers Source not found, and route_evaluations lists only the routes you can read.
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": {
"kind": "<kind>",
"severity": "<severity>"
},
"name": "preview_notification_routing"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | Yes | Notification kind (e.g. cluster_offline, deploy_failed, alert_trigger_fired). | |
| alert_id | No | Alert id (UUID) for alert_trigger_fired, so the alert's own destination list is included. | |
| severity | Yes | One of critical, warning, info. | |
| reference | No | Concrete reference the notification is about, for routes with a reference_pattern: refs/heads/<branch> for a push, pull/<number> for a pull request run, refs/tags/<tag> for a tag. | |
| source_id | No | Source identifier, for kinds that carry one: a delivered alert firing carries the id of its alert. At most 512 bytes and 4 uuids. | |
| cluster_id | No | Cluster the hypothetical notification concerns (UUID); omit for organisation-wide. | |
| application_id | No | Application (UUID) the hypothetical notification is about, for routes scoped to an application (pipeline, image gate and preview notifications carry one). |