Skip to main content
Glama

Add a notification channel

add_channel
Destructive

Add a Slack or Discord webhook, an ntfy topic or a US mobile number. The channel stays off and receives nothing until confirm_channel gets the 6-digit code sent to it (valid 10 minutes). Text messages are charged per message from the prepaid balance: first show the person the disclosure, price, terms and privacy links from get_capabilities (channels.sms), and only after they agree send sms_consent. Never assume consent.

Permission: channels:manage. Ask the person before calling.

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": {
      "type": "<type>",
      "destination": "<destination>"
    },
    "name": "add_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoA label the person will recognise.
typeYesChannel type.
alert_idNoAdd the channel to this alert once it is confirmed.
destinationYesSlack or Discord webhook URL, ntfy topic URL, or US mobile number in E.164 form (+1…).
sms_consentNoRequired for sms, after the person agrees to the text-message disclosure.
ntfy_access_tokenNontfy access token, if the topic needs one.
ntfy_topic_is_privateNoRequired for ntfy: confirm the topic is private.

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only mark this as a non-idempotent, destructive, open-world write; the description adds the behavior that actually matters: the channel is inert until a 6-digit code (10-minute validity) is confirmed, and SMS incurs per-message charges against a prepaid balance. The consent gating and required permission scope are operational constraints not captured by any annotation.

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 resource types, then the confirmation flow, then the SMS compliance obligations, then permission and consent reminders — a sensible order with no filler. It is dense, with colon-and-parenthetical chains in the SMS sentence that take a beat to parse, but every clause carries an actionable rule.

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 7-parameter destructive write with a nested consent object, the description covers the identity of the tool, the follow-up prerequisite, the billing/consent path, and the permission gate. An output schema exists, so return-value details are appropriately omitted.

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 and the schema already documents name, type, destination formats, and the sms_consent/ntfy_topic_is_private constraints. The description goes slightly beyond it by explaining the sequencing and precondition for sms_consent and by pointing at get_capabilities for the disclosure version, which helps an agent fill the nested object correctly.

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 enumerates exactly which channel types are accepted (Slack/Discord webhook, ntfy topic, US mobile number), so the agent knows the resource and its variants immediately. It also distinguishes the create step from confirm_channel, the verification step that must follow.

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?

Gives explicit ordering ('stays off and receives nothing until confirm_channel'), names the prerequisite tool (get_capabilities for channels.sms), names the consent parameter to send (sms_consent), and states an exclusion rule ('Never assume consent'). The permission note plus 'Ask the person before calling' adds a clear pre-call condition rather than leaving it implied.

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.

Resources