Skip to main content
Glama

Delete alert

delete_alert
Destructive

Permanently delete one alert definition together with all of its rules. This also removes the alert's whole firing history and cannot be undone from the portal. To stop an alert that is too noisy, use set_alert_enabled with enabled=false instead: it keeps the history and is reversible. Use delete_alert only when the user asks to delete or remove the alert itself, or to undo an alert that was just created by mistake. Find the alert id with list_alerts and name the alert in the confirmation.

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": {
      "alert_id": "<alert_id>"
    },
    "name": "delete_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
alert_idYesAlert UUID, as returned by list_alerts or create_alert.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description goes further by disclosing exactly what is destroyed (the alert, all its rules, and the entire firing history) and that it cannot be undone from the portal. That is precisely the extra context an agent needs before an irreversible mutation.

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?

The destructive scope is front-loaded in the first sentence, followed by the alternative and the usage condition. Four sentences with no filler, though the closing confirmation instruction is slightly tangential to tool selection.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter destructive tool with no output schema, the description covers scope, irreversibility, the safer alternative, and id discovery. Nothing an agent needs in order to call it correctly is missing.

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 alert_id property already documents that it is a UUID returned by list_alerts or create_alert. The description's 'Find the alert id with list_alerts' largely restates the schema, adding only the confirmation-naming convention, 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 states a specific verb and resource ('Permanently delete one alert definition together with all of its rules') and immediately scopes the blast radius to the firing history. It is clearly distinguishable from sibling tools like set_alert_enabled and delete_alert_destination.

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 gives explicit when-not-to-use guidance ('To stop an alert that is too noisy, use set_alert_enabled with enabled=false instead'), names the reversible alternative, and states the positive condition ('only when the user asks to delete or remove the alert itself, or to undo an alert that was just created by mistake'). It even tells the agent how to obtain the id via list_alerts.

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.