Skip to main content
Glama

Preview notification routing

preview_notification_routing
Read-only

Dry-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

NameRequiredDescriptionDefault
kindYesNotification kind (e.g. cluster_offline, deploy_failed, alert_trigger_fired).
alert_idNoAlert id (UUID) for alert_trigger_fired, so the alert's own destination list is included.
severityYesOne of critical, warning, info.
referenceNoConcrete 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_idNoSource identifier, for kinds that carry one: a delivered alert firing carries the id of its alert. At most 512 bytes and 4 uuids.
cluster_idNoCluster the hypothetical notification concerns (UUID); omit for organisation-wide.
application_idNoApplication (UUID) the hypothetical notification is about, for routes scoped to an application (pipeline, image gate and preview notifications carry one).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / source_id / description
      Previous value: -"Source identifier, for kinds that carry one."New value: +"Source identifier, for kinds that carry one: a delivered alert firing carries the id of its alert. At most 512 bytes and 4 uuids."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond readOnlyHint=true by confirming 'Nothing is sent' and disclosing project-confinement behaviour in detail: foreign clusters/applications answer not found, withheld sources answer 'Source not found', and route_evaluations is filtered to readable routes. That is genuinely useful behavioural context an agent could not infer from annotations.

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?

Front-loads the core action and the 'nothing is sent' guarantee before the usage hint. The final sentence packs several permission-scoping clauses into one dense run-on, mildly hurting readability but every clause carries information.

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

Completeness5/5

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

There is no output schema, yet the description enumerates the return content (reachable destinations, matched/suppressed routes with reasons, fallback usage) and covers the error and visibility edge cases. Nothing essential for correct invocation is missing.

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 baseline is 3, but the description adds value by framing the inputs as a hypothetical notification (kind + severity required, cluster/source/application/reference optional) and by tying reference format to route reference_pattern matching. It does not re-explain each parameter exhaustively, which is appropriate given the schema.

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?

States a specific verb ('Dry-run') on a specific resource ('the organisation's notification routing') and enumerates what the dry run reports: destinations reached, routes matched/suppressed with reasons, and fallback usage. This is clearly distinguishable from sibling tools like create_notification_route, update_notification_route and list_notification_routes.

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

Usage Guidelines4/5

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

Explicitly says 'Use this to verify routing before and after changing routes', which gives a clear trigger context. It also points at list_notification_routes for learning which sources are withheld. It stops short of naming test_notification_route as the contrasting alternative (a real-send vs dry-run decision), so not a full 5.

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.