Skip to main content
Glama

WhatsDownNow

Change an alert stack

update_alert_stack
Idempotent

Add or remove services, add an email or webhook destination, or rename a stack you created. New emails get a confirmation link. Needs the stack id and its management token.

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": {
      "stack_id": "<stack_id>",
      "token": "<token>"
    },
    "name": "update_alert_stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
tokenYesManagement token (wdn_...) returned once by create_alert_stack
stack_idYesStack id (stk_...) returned by create_alert_stack
add_emailNoAnother email address to notify (must confirm)
add_servicesNoSlugs or names to start watching (default rules)
add_webhook_urlNoAnother https webhook (Slack/Discord/JSON) to notify
remove_servicesNoSlugs or names to stop watching

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 this a non-read-only, idempotent, non-destructive, open-world mutation, so the safety profile is covered. The description adds genuinely useful behavior the annotations do not: adding an email is not immediate because 'New emails get a confirmation link', and both the stack id and the one-time management token are required. It does not say what the call returns or whether removals take effect immediately.

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 sentences, with the set of operations front-loaded and the prerequisites placed after it. No filler, no restatement of the title, and every clause conveys an operation or a precondition the agent needs.

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 7-parameter mutation tool with high schema coverage and annotations that carry most of the safety signals, the description is nearly sufficient. The one remaining gap is that it says nothing about what a successful call returns, which matters because there is no output schema to compensate.

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 description coverage is 86%, which already establishes the baseline of 3 for all seven parameters. The description goes beyond that by explaining the confirmation-link behavior for add_email's webhook and email destinations and by pairing stack_id with its token requirement. The only remaining gap is that it does not specify whether the services arrays are pushed independently or atomically within a single call.

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?

The description uses concrete verbs (add, remove, rename) against a specific resource (alert stack) and enumerates the mutable facets: services, email/webhook destinations, and the name. It does not explicitly name siblings such as rotate_alert_stack_key or delete_alert_stack, so the boundary with those tools must be inferred, but the purpose itself is unambiguous.

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 enumerated operations and by the ownership constraint 'a stack you created', which tells the agent this is not for stacks it does not own. It also states the prerequisites (stack id plus management token). It never says when to prefer a sibling (for example key rotation or deletion) or on what basis.

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.