Skip to main content
Glama

Rename or pause an alert

edit_alert
DestructiveIdempotent

Rename an alert, pause it, or both. Needs edit_revision from get_alert. Cannot resume, change filters or start paid work. Pausing stops future checks; checks already running finish and are charged.

Permission: alerts:write.

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>",
      "edit_revision": "<edit_revision>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "edit_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew alert name.
statusNoSend "paused" to pause the alert.
alert_idYesAlert ID.
edit_revisionYesedit_revision from get_alert. The edit fails if the alert changed since.
idempotency_keyYesA new random key (16–100 letters, digits, - or _) for each request. Reuse it only to retry the identical request.

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and idempotentHint=true, but the description adds the substance behind them: pausing stops future checks, already-running checks finish and are still charged, the edit fails if the alert changed since edit_revision was read, and the call requires alerts:write. That is real consequence and permission disclosure beyond structured fields.

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?

Four short sentences with the core action first, then prerequisite, then exclusions, then cost/charging caveat and permission. No filler, and the most decision-relevant content is front-loaded.

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 5-parameter mutation tool with an output schema (so return values need not be explained) and full schema coverage, the description covers action, precondition, exclusions, side effects, and required permission. Nothing an agent needs in order to invoke 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 description coverage is 100%, so name, status, alert_id, edit_revision, and idempotency_key are already documented in the schema. The description reinforces that edit_revision must come from get_alert, but this largely repeats the schema text rather than adding new meaning, 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?

The description opens with a precise verb+resource statement: 'Rename an alert, pause it, or both.' It then bounds the scope with 'Cannot resume, change filters or start paid work,' which separates it cleanly from siblings like get_alert, set_alert_channels, and start_alert_in_app.

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 states a hard prerequisite ('Needs edit_revision from get_alert') and explicit exclusions ('Cannot resume, change filters or start paid work'), which is strong when-to-use/when-not guidance. It stops short of naming what to call instead for the excluded operations, so it is clear context rather than a full routing decision.

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.

Resources