Skip to main content
Glama
vmware-skills

vmware-aria

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

cancel_alert

Destructive

Permanently close active VMware Aria alerts by canceling them. Preview the alert's blast radius before confirming to ensure the right alert is dismissed.

Instructions

[WRITE] Cancel (dismiss) an active alert. This WRITE operation permanently closes the alert.

Use acknowledge_alert instead if you only want to mark it as seen. Cancelled alerts will not re-trigger unless the underlying condition recurs.

Without confirm=True this only previews: it returns blast_radius (alert id, definition, criticality, status, and the resource it is on) and changes nothing. Show that to the user and get their explicit decision. Do not set confirm=True on your own because the user asked earlier: they have not seen what it changes yet. An alert already cancelled returns action "noop". Refused with confirm=True: an alert whose status or resource cannot be read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNoAria target name from config; default when omitted.
confirmNoFalse (default) returns the blast radius and changes nothing. True applies it.
alert_idYesThe alert UUID to cancel.
confirmedNoDeprecated alias for confirm; removed in the next minor release. confirmed=False holds even when confirm=True.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.16.0
    • addedInput schema / properties / confirm
      Added value: +{
+  "default": false,
+  "description": "False (default) returns the blast radius and changes nothing. True applies it.",
+  "title": "Confirm",
+  "type": "boolean"
+}
    • addedInput schema / properties / confirmed / anyOf
      Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / confirmed / default
      Previous value: -falseNew value: +null
    • changedInput schema / properties / confirmed / description
      Previous value: -"Must be True to actually cancel. Default False = preview only."New value: +"Deprecated alias for confirm; removed in the next minor release. confirmed=False holds even when confirm=True."
    • removedInput schema / properties / confirmed / type
      Removed value: -"boolean"
  2. Changed4 schema fields changedv1.10.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / alert_id / description
      Added value: +"The alert UUID to cancel."
    • addedInput schema / properties / confirmed / description
      Added value: +"Must be True to actually cancel. Default False = preview only."
    • addedInput schema / properties / target / description
      Added value: +"Aria target name from config; default when omitted."
  3. Addedv1.5.29
  4. Removedv1.5.28
  5. Changed1 schema field changedv1.5.18
    • addedInput schema / properties / confirmed
      Added value: +{
+  "default": false,
+  "title": "Confirmed",
+  "type": "boolean"
+}
  6. First observedv1.3.2

TDQS

A4.8/5.0
Behavior5/5

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

Beyond annotations (destructiveHint=true, readOnlyHint=false), the description discloses that cancellation is permanent, alerts will not re-trigger unless the condition recurs, already-cancelled alerts return 'noop', and confirmation is refused for unreadable alerts. It also explains the preview behavior in detail, adding substantial behavioral context that annotations alone do not convey.

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 description is front-loaded with the core purpose and then structured into clear usage and behavioral notes. It is longer than strictly necessary, with some redundancy (WRITE appears twice), but every section contributes essential safety and edge-case information for a destructive confirmation-gated operation. The structure makes it readable and scannable.

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?

Given that this is a destructive, confirmation-gated write operation with no output schema, the description is remarkably complete. It covers the main action, the alternative tool, the preview/confirm workflow, the no-op case, the non-retrigger behavior, and the refusal condition. An agent has everything it needs to invoke the tool correctly and safely in an interactive context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema covers all parameters with descriptions, so the baseline is 3. The description adds meaningful semantics for the crucial 'confirm' parameter: without it the tool only previews and changes nothing; with it the operation applies. This goes beyond the schema's simple 'False returns blast radius, True applies it' by explaining the expected user-decision flow. No additional clarity is needed for other parameters since the schema already documents them well.

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: 'Cancel (dismiss) an active alert' and clarifies it is a WRITE operation that permanently closes the alert. It distinguishes itself from acknowledge_alert, which is a sibling tool, by explicitly explaining the difference. This leaves no ambiguity about what the tool does.

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?

The description gives explicit when-to-use guidance: use acknowledge_alert if you only want to mark as seen. It also explains the preview-vs-confirm flow and instructs the agent to show the blast radius to the user and get explicit decision before setting confirm=True. This is actionable routing and safety guidance beyond any structured field.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools