Skip to main content
Glama

Replace an alert’s search

approve_alert_update
DestructiveIdempotent

Replace the alert’s sources and criteria with the quoted preview and leave it paused. Revokes earlier monitoring permissions. Call only after the person approves this exact change.

Permission: monitoring:manage. Ask the person before calling.

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": {
      "update_id": "<update_id>",
      "request_hash": "<request_hash>"
    },
    "name": "approve_alert_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
update_idYesThe update ID returned when it was quoted or created.
request_hashYesThe exact request_hash from the quote. Approval fails if anything changed since the quote.

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, yet the description adds consequences the annotations cannot express: the alert is left paused and earlier monitoring permissions are revoked. It also discloses the required scope (monitoring:manage) and the human-approval gate, which is exactly the kind of context an agent needs before firing a destructive call.

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?

Three short sentences, front-loaded with the action and its end state, then the side effect, then the permission and consent gate. Nothing is repeated from the title and no sentence is 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?

Output schema exists, so return values need no explanation; the description covers the missing pieces an agent needs — irreversible-ish side effects, resulting paused state, required permission, and the mandatory human approval step. Nothing material is left out for a two-parameter destructive mutation.

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 already carry descriptions explaining update_id and the request_hash tamper check. The description's phrases 'the quoted preview' and 'this exact change' gesture at the same idea but add no new syntax, sourcing, or failure detail beyond the schema.

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 names a specific verb and resource ('Replace the alert's sources and criteria') plus the exact state it leaves behind ('leave it paused'). The reference to 'the quoted preview' cleanly separates it from quote_alert_update, get_alert_update, and cancel_alert_update in the sibling set.

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 gives an explicit precondition: 'Call only after the person approves this exact change' and 'Ask the person before calling.' That is a clear gating condition, but it never names the preceding sibling step (quote_alert_update) or states what to do instead when the quote is stale — the schema only hints at that via request_hash.

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