Skip to main content
Glama

WhatsDownNow

Delete an alert stack

delete_alert_stack
DestructiveIdempotent

Permanently delete a stack and stop all its alerts. Only do this when the user asks. 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": "delete_alert_stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesManagement token (wdn_...) returned once by create_alert_stack
stack_idYesStack id (stk_...) returned by create_alert_stack

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description adds real context on top: the deletion is permanent, alerts stop firing as a side effect, and a management token is required for authorization. It doesn't say what happens if the stack is already gone or whether the token is invalidated, but the key consequences are disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with the destructive outcome front-loaded. The final sentence mostly repeats what the required-parameters schema already enforces, so it is slightly redundant but not bloated.

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 two-parameter destructive mutation with full schema coverage and annotations carrying the safety profile, the description covers purpose, consequence, and the authorization prerequisite. No output schema exists and none is needed for a delete operation.

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 schema already documents both the stack_id format/pattern and that the token comes from create_alert_stack. The description's sentence restates that both are needed but adds no syntax or format detail beyond the schema, so the 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?

States a specific verb and resource ("Permanently delete a stack") plus the immediate consequence ("stop all its alerts"), which separates it cleanly from create/get/update/rotate siblings without needing to name them.

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?

"Only do this when the user asks" is an explicit usage guard that tells the agent not to invoke this proactively or on inference. It stops short of naming alternatives (e.g., update_alert_stack for modification), but the when-to-use condition is clear.

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.