Rius

Delete Alert Channel

delete_alert_channel

Destructive

Delete a notification channel. Irreversible.

Takes two calls, like delete_alert_rule: once to preview, once with the phrase.

Any rule still pointing at this channel loses that destination silently and falls back to the region's default webhook — it does not start failing loudly. Consider update_alert_channel with enabled false instead, which is reversible.

Needs the channels:manage capability.

channel_id: the channel's id, from list_alert_channels. confirm: the phrase from the first call's output. workspace: optional workspace id, name, or org-name/workspace-name when the same name occurs in two of your orgs (defaults to your default).

Example:

Remove the old ops webhook.

{ "name": "delete_alert_channel", "arguments": { "channel_id": "8a1…" } }

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": {
      "channel_id": "<channel_id>"
    },
    "name": "delete_alert_channel"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	No
`workspace`	No
`channel_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes well beyond the destructiveHint=true annotation by disclosing the silent side effect on dependent rules ('loses that destination silently ... does not start failing loudly'), the required `channels:manage` capability, and the two-phase confirmation requirement. These are exactly the behavioral facts an agent cannot 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-loaded with the destructive verb and irreversibility, then consequence, then alternative, then auth, then params. Well ordered, but the trailing example block restates argument shape that the schema and the preceding param sentences already cover, adding some length without new 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?

For a destructive, capability-gated tool with an output schema, the description covers consequences, prerequisites, the confirm handshake, and parameter sourcing. Nothing needed to invoke it safely is missing, and return values are rightly left to the output schema.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full load and does: channel_id is sourced from list_alert_channels, confirm is the phrase from the first call's output, and workspace accepts id/name or org-name/workspace-name with a default. All three parameters are disambiguated beyond their bare types.

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 channel') and immediately qualifies it with 'Irreversible.' It also names related siblings (delete_alert_rule, list_alert_channels, update_alert_channel), so an agent can place it precisely in the tool graph.

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

Usage Guidelines5/5

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

Explicitly gives a when-not-to-use path: 'Consider update_alert_channel with enabled false instead, which is reversible.' It also documents the two-call preview+confirm flow, which is non-obvious invocation guidance rather than mere context.

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

All Rius tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.