Skip to main content
Glama

Create alert destination

create_alert_destination
Destructive

Create a channel-based alert destination: a Slack channel the organisation's Ankra Slack app posts to, or a Microsoft Teams channel the Ankra bot is installed in. The channel must come from list_alert_destination_channels. Webhook destinations (Discord, PagerDuty, custom webhooks, Slack incoming webhooks) carry their URL as a credential and are created in the portal or with the CLI, never here. A new destination receives nothing until a notification route points at it (create_notification_route).

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

Input Schema

NameRequiredDescriptionDefault
nameYesDestination name, unique in the organisation.
enabledNoWhether the destination delivers (default true).
templateNoOptional message template; omit for the default.
channel_idYesChannel id from list_alert_destination_channels.
descriptionNoOptional description.
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.4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses two non-obvious behaviors: a newly created destination delivers nothing until a notification route references it, and URL-bearing webhook destinations are deliberately unsupported here for credential-handling reasons. The annotations flag destructiveHint=true, but the description never explains what makes this create operation destructive or whether it can be undone, which is the main remaining gap.

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 sentences, each carrying distinct load: what it creates, what it refuses, and what must follow. The supported-type constraint is front-loaded and the exclusions come before any follow-up advice, so no sentence is padding.

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 6-parameter mutation with no output schema, the definition covers prerequisites, exclusions, and the downstream dependency on create_notification_route. It omits what the call returns (an id needed by the route tool) and any permission or authorisation requirements, which leaves a small but real hole for an agent chaining these calls.

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 description coverage is 100%, so every parameter is already documented, including the slack/teams enum semantics and the unique-name constraint. The description reinforces the channel_id provenance requirement (must come from list_alert_destination_channels) but adds no format, syntax, or validation detail beyond the schema, so baseline 3 applies.

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?

The description opens with a specific verb+resource pair ("Create a channel-based alert destination") and immediately narrows scope to the two supported channel types (Slack channel via the Ankra app, Teams channel via the Ankra bot). It explicitly distinguishes this tool from the webhook-destination path, so an agent can tell which tool handles Discord/PagerDuty/custom webhooks without inspecting sibling schemas.

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?

It states the prerequisite ("The channel must come from list_alert_destination_channels"), the exclusion (webhook destinations are created in the portal or CLI, never here), and the required follow-up (a new destination receives nothing until create_notification_route points at it). When-to-use, when-not-to-use, and the alternative are all explicit.

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.