Skip to main content
Glama

Update notification route

update_notification_route
Destructive

Update one notification route in place. Only the fields you pass change; passing a field explicitly empty clears it (e.g. severity "" removes the severity filter), except a filter withheld from you (the route's scope_note), which stays as it is. Changing mode to exclude, or disabling a route, changes what gets delivered - verify with preview_notification_routing afterwards.

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": "update_notification_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoReplace the single-kind filter; empty clears it.
modeNoinclude delivers matches; exclude suppresses them.
kindsNoReplace the kinds list.
enabledNoEnable or disable the route.
priorityNoEvaluation order, lower first.
route_idYesNotification route id (UUID) from list_notification_routes.
severityNoReplace the severity filter; empty clears it.
source_idNoReplace the source filter; null or empty clears it (an empty source is never stored as a filter), except a source filter withheld from you (the route's scope_note), which stays as it is. At delivery today a notification's source is the id of the alert that fired, so filter on an alert id. At most 512 bytes and 4 uuids. A source you may not read answers Source not found, as preview_notification_routing does.
cluster_idNoReplace the cluster filter (UUID); null or empty clears it, except a cluster filter withheld from you (the route's scope_note), which stays as it is.
kinds_negatedNoInvert the kinds list.
stop_on_matchNoStop evaluating lower-priority routes on match.
application_idNoReplace the application filter (UUID); null or empty clears it, except an application filter withheld from you (the route's scope_note), which stays as it is.
destination_idNoRe-point the route at another alert destination (UUID).
reference_patternNoReplace the branch/tag/pull request glob filter (e.g. main, release/*, pull/*); empty clears it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / application_id / description
      Previous value: -"Replace the application filter (UUID); empty clears it."New value: +"Replace the application filter (UUID); null or empty clears it, except an application filter withheld from you (the route's scope_note), which stays as it is."
    • changedInput schema / properties / application_id / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedInput schema / properties / cluster_id / description
      Previous value: -"Replace the cluster filter (UUID); empty clears it."New value: +"Replace the cluster filter (UUID); null or empty clears it, except a cluster filter withheld from you (the route's scope_note), which stays as it is."
    • changedInput schema / properties / cluster_id / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedInput schema / properties / source_id / description
      Previous value: -"Replace the source filter; empty clears it, except a source filter withheld from you (the route's scope_note), which stays as it is."New value: +"Replace the source filter; null or empty clears it (an empty source is never stored as a filter), except a source filter withheld from you (the route's scope_note), which stays as it is. At delivery today a notification's source is the id of the alert that fired, so filter on an alert id. At most 512 bytes and 4 uuids. A source you may not read answers Source not found, as preview_notification_routing does."
    • changedInput schema / properties / source_id / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / source_id / description
      Previous value: -"Replace the source filter; empty clears it."New value: +"Replace the source filter; empty clears it, except a source filter withheld from you (the route's scope_note), which stays as it is."
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the destructiveHint=true/idempotentHint=false annotations, the description explains the partial-update contract (untouched fields persist), the destructive consequence that an explicitly empty value clears a filter, and the important carve-out that a withheld scope_note filter is never cleared. It also flags that mode=exclude or disabling changes delivery. Gaps remain on error behavior for unknown route_ids and whether a failed update is atomic, which keeps it off a 5.

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

Conciseness4/5

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

Three compact sentences ordered by importance: what it does, how partial updates behave, then the risk/verification note. The empty-clears rule is stated globally even though individual schema fields repeat it, which is slight redundancy but aids scanning.

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?

For a 14-parameter destructive mutation with no output schema, the description covers the semantics an agent most needs: partial update, clearing behavior, the hidden-filter exception, and a verification step. Missing only failure/rollback behavior and permission requirements.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns above that by generalizing the clear-on-empty rule across all filters and calling out the scope_note exception that applies to source_id/cluster_id/application_id. It still defers per-field details (enums, byte limits, evaluation order) to the schema rather than restating them.

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

Purpose4/5

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

The opening sentence states a specific verb and resource ('Update one notification route in place') and the rest clarifies the partial-update scope, which separates it from create/delete siblings. It stops short of naming those siblings as alternatives, but the operation is unambiguous.

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?

It tells the agent to verify with preview_notification_routing after changing mode or disabling, which is useful post-action guidance. It gives no explicit when-to-use-this-vs-create_notification_route/get_notification_route guidance or prerequisites (e.g. needing a route_id from list_notification_routes, which only the schema says).

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.