Get notification route
get_notification_routeRead one notification route you can read (the scope list_notification_routes reports): its kind, severity, cluster, source, application and reference filters, its destination, priority, include/exclude mode, stop-on-match and whether it is enabled. A route another project owns answers not found, like a missing one, and the answer names the scope it was read in. A cluster, application or source filter you cannot read is withheld: its cluster_id, application_id or source_id reads as null and the route's scope_note says so, so that null does not mean every cluster, application or source. A source_id is withheld when any id in it, the whole source_id or one part of a composite one such as / or :, names a cluster, application, ticket, pipeline run or step, pipeline repository, automation, workspace, incident, environment or API token of another project or of no project, an execution, power schedule, application installation, sandbox environment, agent task or support ticket on such a cluster, or an alert a rule of which names a cluster outside your project, or that is deleted; so is a source_id longer than 512 bytes or carrying more than 4 uuids, which no write accepts any more. Any other source_id, and every reference_pattern, is shown as written. At delivery today a notification's source is the id of the alert that fired, so a source filter matches an alert's id. Read-only.
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": {
"route_id": "<route_id>"
},
"name": "get_notification_route"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| route_id | Yes | Notification route id (UUID) from list_notification_routes. |