Skip to main content
Glama

List alert destination channels

list_alert_destination_channels
Read-only

List the channels a channel-based alert destination can deliver to: the Slack channels the organisation's Ankra Slack app can post to, or the Microsoft Teams channels of every team the Ankra bot is installed in. Use the ids with create_alert_destination. Read-only.

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": {
      "integration_type": "<integration_type>"
    },
    "name": "list_alert_destination_channels"
  }
}

Input Schema

NameRequiredDescriptionDefault
integration_typeYesslack for a Slack channel the organisation's Ankra Slack app posts to, teams for a Microsoft Teams channel the Ankra bot is installed in.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the trailing 'Read-only' is largely redundant. The description does add real behavioral context beyond the annotations: the result set is scoped to what the org's Slack app can post to or where the Teams bot is installed, which explains empty or partial results.

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 tight sentences, front-loaded with the resource and scope, followed by the follow-up action. No filler; only the redundant 'Read-only' trailers slightly duplicate the annotations.

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?

For a single-parameter read tool with no output schema, the description covers scope, the two integration types, and the intended consumer of the returned ids. The one gap is that the return shape is only implied ('the ids') rather than stated.

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?

Schema coverage is 100% and the single enum parameter is already documented in the schema, so the description's slack/teams explanation mostly restates it. Baseline 3 applies since the schema carries the parameter semantics.

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 ('List the channels a channel-based alert destination can deliver to') and enumerates the two variants it covers, Slack channels via the Ankra Slack app and Teams channels where the bot is installed. It is distinguishable from the nearby list_alert_destinations, but it never names that sibling explicitly, so an agent must infer the boundary.

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?

Gives a concrete downstream usage instruction ('Use the ids with create_alert_destination'), which tells the agent why to call it and what to do with the result. It does not state when not to call it or point to alternatives such as get_alert_destination or list_alert_destinations.

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.