Skip to main content
Glama

Update alert destination

update_alert_destination
Destructive

Update an alert destination's name, description, message template or enabled flag. Only the fields you pass change. Disabling a destination stops every notification routed to it. A destination's URL or channel is changed in the portal or with the CLI, never here.

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": {
      "destination_id": "<destination_id>"
    },
    "name": "update_alert_destination"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew name, unique in the organisation.
enabledNoEnable (true) or disable (false) delivery.
templateNoNew message template.
descriptionNoNew description.
destination_idYesAlert destination id (UUID) from list_alert_destinations.

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?

Annotations already declare destructiveHint=true and idempotentHint=false; the description adds real context on top by warning that disabling a destination stops every notification routed to it and by clarifying that omitted fields are preserved. It does not mention permissions, immediate effect, or duplicate-name failure behavior, so it stops short of full disclosure for a mutation tool.

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, each earning its place: scope first, update semantics second, the destructive consequence third, with the exclusion last. Nothing is repeated from the schema or annotations verbatim.

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 one-required, five-parameter destructive mutation with no output schema, the description covers the mutable surface, the merge semantics, and the main side effect. Minor gaps remain around permission requirements, immediate-vs-eventual effect, and error handling for the org-unique name constraint.

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, but the description adds meaning the schema lacks: the partial-update contract for all optional fields and the fact that the destination's URL or channel is not a parameter here at all. The consequence of the enabled flag is also spelled out beyond the schema's 'Enable (true) or disable (false) delivery.'

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 and resource ('Update an alert destination') and enumerates exactly which fields are mutable (name, description, message template, enabled flag). It also explicitly carves out what this tool does not touch (URL/channel), so the agent can distinguish it from create/delete/get siblings without opening a schema.

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?

It clearly states partial-update semantics ('Only the fields you pass change') and redirects URL/channel changes to the portal or CLI, which is genuine when-not-to-use guidance. It stops short of pointing to a specific alternative for the enabled flag even though a dedicated toggle sibling exists, leaving that overlap for the agent to resolve.

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.