Skip to main content
Glama

Choose where an alert sends results

set_alert_channels
DestructiveIdempotent

Replace the confirmed channels an alert sends results to. [] keeps results in Poacher only. Starts no paid work; a text-message channel is charged per message when results arrive (price in get_capabilities, channels.sms).

Permission: channels:manage.

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": {
      "alert_id": "<alert_id>",
      "channel_ids": "<channel_ids>"
    },
    "name": "set_alert_channels"
  }
}

Input Schema

NameRequiredDescriptionDefault
alert_idYesAlert ID.
channel_idsYesConfirmed channel IDs. [] for none.

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations by specifying full-replacement semantics (existing channel list is overwritten), the cost model (no work started now, SMS charged per message on delivery, price at get_capabilities channels.sms), and the required permission channels:manage. That is exactly the destructive/auth/cost disclosure an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences: action first, empty-case semantics second, cost and permission last. Nothing is redundant and nothing is buried.

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

Completeness4/5

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

Covers replacement scope, empty input, cost, and permission for a two-parameter mutation, and an output schema exists so return values need not be explained. The only gap is what happens when passing IDs that are not confirmed or already attached.

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 both parameters are already documented. The description nonetheless adds real meaning to the empty-array case ('[] keeps results in Poacher only'), which the schema only states as '[] for none'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Replace the confirmed channels an alert sends results to.' The word 'Replace' and the qualifier 'confirmed' distinguish it from the add_channel and confirm_channel siblings without naming them.

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

Usage Guidelines3/5

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

Usage is only implied: the replacement framing and the '[] keeps results in Poacher only' note tell the agent what happens, but it never says when to use this instead of add_channel or confirm_channel, nor whether unconfirmed IDs are rejected.

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