Skip to main content
Glama

List notification routes

list_notification_routes
Read-only

List 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

NameRequiredDescriptionDefault
enabled_onlyNoOnly routes that are currently enabled.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare readOnlyHint=true; the description goes well beyond that by disclosing result scoping (one project's routes plus organisation-wide routes, organisation-wide alone, or all routes), that other projects' routes are omitted but may exist, and that unreadable cluster/application/source filters are returned as null with a scope_note explaining why. The explicit warning that a null does not mean "every cluster" is exactly the kind of non-obvious behavior an agent cannot infer from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in a strong first sentence, but the bulk is a roughly 150-word chained sentence enumerating every entity type whose id causes a source_id to be withheld, plus a 512-byte/4-uuid rule. That edge-case enumeration is disproportionate for a one-parameter list tool and is harder to absorb than the core scoping rules it follows.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the full burden of explaining return semantics, and it does: result scope, scope_note, null-withholding, and how source filters map to alert ids at delivery today. It stops short of ordering, pagination or result-size behavior, which are relevant for a list endpoint that can return organisation-wide routes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single parameter enabled_only is fully documented in the schema, so the baseline of 3 applies. The description adds no meaning beyond it — it never mentions the enabled filter or how it interacts with the read scope.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"List the notification routes you can read" gives a specific verb and resource, and the appositive defines the domain object (rules that filter platform notifications by kind, severity, cluster and source onto alert destinations, with priority, include/exclude mode, stop-on-match). This distinguishes it from get_notification_route, create/update/delete_notification_route and from destination-oriented siblings like list_alert_destinations without needing the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the description explains what scope of results will be read depending on whether the caller acts in or is confined to a project, which helps an agent predict coverage, but never says when to choose this over get_notification_route, preview_notification_routing or test_notification_route. No when-not-to-use guidance or prerequisites are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.