Skip to main content
Glama

List notification channels

list_channels
Read-onlyIdempotent

List this account’s channels (email, Slack, Discord, ntfy, web push, text) and whether each is on, paused, opted out or waiting for its code. Destinations and credentials are never returned.

Permission: channels:manage.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_channels"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered elsewhere. The description still adds real context beyond that: it discloses that destinations and credentials are never returned (telling the agent not to expect secret material) and states the required permission "channels:manage". It does not mention pagination or result size, a minor omission.

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?

Two short sentences plus a one-line permission note. The core capability and its enumeration are front-loaded, the security caveat follows, and no sentence is redundant or restates the tool name.

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?

An output schema exists, so the description need not explain return shape, and it still names the states returned. With the permission requirement and the credentials caveat included, an agent has enough to call it correctly; the only gap is the absence of guidance on when to prefer get_channel or the list_* siblings.

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?

The tool takes zero parameters ({}) and the description correctly describes no inputs, so there is no parameter meaning to compensate for. Baseline 4 applies; nothing in the description contradicts or misdescribes the empty schema.

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?

"List this account's channels" pairs a specific verb with a specific resource, and the parenthetical enumerates the channel types (email, Slack, Discord, ntfy, web push, text) plus the four states returned, so the agent knows exactly what scope and outcome to expect. It does not distinguish itself from siblings such as get_channel or list_alerts, which keeps it out of the top band.

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 implied by the enumeration: an agent can infer this is the way to discover which channels exist and their current state. However, there is no explicit when-to-use framing and no pointer to alternatives (e.g. get_channel for a single channel, add_channel to create one), so the agent must infer routing from names alone.

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