Skip to main content
Glama

Delete notification route

delete_notification_route
Destructive

Delete a notification route. Notifications it delivered stop reaching its destination (unless another route or an alert's own channel list still covers them), and notifications it excluded start flowing again - check the blast radius with preview_notification_routing first.

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

Input Schema

NameRequiredDescriptionDefault
route_idYesNotification route id (UUID) from list_notification_routes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description goes further by spelling out the blast radius: delivered notifications stop arriving unless another route or an alert's own channel list still covers them, and excluded notifications resume. That is genuinely additive context beyond the annotations, though it omits irreversibility and permission requirements.

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?

Two sentences, front-loaded with the action, then the consequences and the recommended pre-check. The parenthetical exception clause is dense and slightly tangled but carries real information, so no trimming is warranted.

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?

For a single-parameter destructive tool with no output schema, the description covers the action, the downstream effects including edge cases, and the safe pre-flight step. Nothing an agent needs to call this correctly 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?

There is a single parameter with 100% schema description coverage naming it as a UUID from list_notification_routes. The description adds nothing about route_id, so the schema carries the load and the baseline 3 applies.

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 and resource ("Delete a notification route") and immediately describes the semantic effect on routing, which separates it from update_notification_route, delete_alert_destination and the other delete_* siblings. An agent can identify the operation without opening 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 Guidelines4/5

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

Explicitly routes the agent to preview_notification_routing before calling, which is a concrete alternative/precondition. It does not say when not to delete (e.g. to merely disable or retarget, use update_notification_route), so it falls just short of full when/when-not coverage.

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.