List notification routes
list_notification_routesList the notification routes you can read - the rules that filter platform notifications by kind, severity, cluster and source onto alert destinations, with priority, include/exclude mode and stop-on-match. The result's scope says what was read: one project's routes plus the organisation-wide routes every project shares (when you act in or are confined to a project), the organisation-wide routes alone, or every route of the organisation. When it is one project, routes other projects own are not listed and may exist. 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
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "list_notification_routes"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| enabled_only | No | Only routes that are currently enabled. |