Skip to main content
Glama

Get notification route

get_notification_route
Read-only

Read 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

NameRequiredDescriptionDefault
route_idYesNotification route id (UUID) from list_notification_routes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only supply readOnlyHint, and the description goes well beyond that: cross-project routes return not found, and the answer names the scope it was read in. It also explains the redaction behaviour in detail, that withheld cluster/application/source filters surface as null with a scope_note, and the exact rules under which a source_id is withheld.

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 correctly, but the bulk of the text is one enormous run-on sentence cataloguing dozens of entity types (tickets, pipeline runs, sandboxes, API tokens, power schedules) that govern source_id withholding. That enumeration is far more granular than an agent needs to choose and call this tool, and it buries the actionable content.

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, so the description carries the burden of describing the response, and it does: the field list, the null-plus-scope_note redaction signal, the not-found case, and the note that a source filter matches an alert id today. Nothing needed to interpret the result is missing.

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 coverage is 100% and the single route_id parameter is already documented as a UUID from list_notification_routes. The description reinforces the provenance of the id and adds the consequence of an unreadable or foreign id, but nothing about the parameter's format beyond what the schema states.

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?

Opens with a specific verb and resource ("Read one notification route you can read") and then enumerates exactly what is returned: kind, severity, cluster, source, application and reference filters, destination, priority, include/exclude mode, stop-on-match and enabled flag. This clearly separates it from list_notification_routes, update_notification_route and delete_notification_route.

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?

It anchors usage by saying the route must be one within the readable scope reported by list_notification_routes, and that a route owned by another project answers not found rather than leaking data. It does not explicitly contrast with siblings like preview_notification_routing or test_notification_route, but the retrieval context is unambiguous.

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.