Skip to main content
Glama

Set alert enabled

set_alert_enabled
Destructive

Enable or disable one alert. Disabling is the reversible mute: the alert and its whole firing history are kept, it still appears in the alerts list marked disabled, and any incident it still has open is settled so it stops reporting as firing. For an alert ingested from an external source (source 'external', e.g. delivered from Alertmanager) disabling also stops new incidents being created from further deliveries - but it does NOT touch the upstream Prometheus rule, which keeps firing where it is defined, so say so rather than claiming the alert itself was removed. Re-enabling resumes ingest. Find the alert id with list_alerts. Prefer this over deleting an alert: deletion also removes the firing history and cannot be undone from the portal.

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>",
      "enabled": "<enabled>"
    },
    "name": "set_alert_enabled"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYestrue to enable the alert, false to mute it.
alert_idYesAlert UUID, as returned by list_alerts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: history is retained, the alert still appears in the list as disabled, open incidents are settled, and for external-source alerts new incident creation stops while the upstream Prometheus rule keeps firing. That last caveat is genuinely useful phrasing guidance. There is a mild tension with destructiveHint=true — the description frames disable as a reversible mute, so an agent may want to know why the flag is set to destructive; that nuance is not resolved.

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?

Front-loads the core action and the reversibility claim before the external-source caveat and the delete comparison. The middle sentence is long and clause-heavy, but each clause carries distinct behavioral information rather than filler.

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 two-parameter toggle with no output schema, the description covers what changes, what is preserved, what is side-effected (open incidents), how external sources behave, how to obtain the id, and why not to use deletion instead. Nothing an agent needs to call this 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 both parameters are already documented (boolean enabled, UUID alert_id), so the schema carries the load. The description adds only the pointer to list_alerts for obtaining the id and the note that re-enabling resumes ingest — helpful but marginal beyond the schema baseline.

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?

Opens with a specific verb+resource pair: "Enable or disable one alert." It immediately distinguishes itself from siblings by naming list_alerts (id discovery) and delete_alert (the destructive alternative), so an agent can place it without inspecting 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?

Gives explicit routing: find the id via list_alerts, and prefer this over deleting an alert because deletion removes firing history and is irreversible. It also scopes behavior for externally-sourced alerts, so the agent knows when the tool's effect differs from expectation.

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.