Skip to main content
Glama

Cancel an alert update

cancel_alert_update
DestructiveIdempotent

Cancel an unapproved replacement. Does not undo an applied change.

Permission: monitoring:manage.

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

Input Schema

NameRequiredDescriptionDefault
update_idYesThe update ID returned when it was quoted or created.

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds genuinely new context: the operation only applies to unapproved updates, it does not revert an applied change, and it requires the monitoring:manage permission. It does not say what happens if the update was already applied (error vs no-op), which keeps it below a 5.

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, all front-loaded: the action, the boundary, then the permission. Nothing is redundant and every sentence carries information an agent needs.

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?

An output schema exists and annotations cover the safety profile, so the description does not need to explain return values. It supplies the state precondition and permission requirement that the structured fields lack. A note on the outcome when the update is already applied (error versus no-op) would close the remaining gap.

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?

There is a single parameter with 100% schema description coverage, including format and pattern, so the schema fully documents it. The description adds no syntax, sourcing, or format detail beyond the schema's own note that the ID comes from quoting or creating. This is the baseline 3 case for high coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: cancel an unapproved replacement (alert update). The word 'replacement' is slightly indirect versus the tool name's 'alert update', but combined with 'unapproved' it scopes the operation to pending, not-yet-applied updates. It does not name a sibling such as cancel_alert_creation, so it falls short of a 5.

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?

'Cancel an unapproved replacement. Does not undo an applied change.' gives a clear state precondition and an explicit when-not boundary. It stops short of naming the alternative tool to use for reverting an applied change, so the guidance is clear but not fully routed.

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