Skip to main content
Glama
vmware-skills

vmware-aria

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_alert_definition

Destructive

Permanently delete an alert definition from Aria Operations. Preview the blast radius first, then confirm to remove. Active alerts remain unaffected.

Instructions

[WRITE] Permanently delete an alert definition. Irreversible.

This WRITE operation removes the alert definition from Aria Operations. Active alerts generated by this definition will not be affected. Use set_alert_definition_state(enabled=False) instead to silence a definition you may want back.

Without confirm=True this only previews: it returns blast_radius (the definition's id, name, adapter and resource kind, criticality and state count) and deletes 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 deletes yet. Refused with confirm=True: a definition that 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.
confirmedNoDeprecated alias for confirm; removed in the next minor release. confirmed=False holds even when confirm=True.
definition_idYesAlert definition id to delete (from list_alert_definitions).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 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 delete. 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"
    • changedInput schema / properties / definition_id / description
      Previous value: -"Alert definition UUID to delete."New value: +"Alert definition id to delete (from list_alert_definitions)."
  2. Changed4 schema fields changedv1.10.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / confirmed / description
      Added value: +"Must be True to actually delete. Default False = preview only."
    • addedInput schema / properties / definition_id / description
      Added value: +"Alert definition UUID to delete."
    • addedInput schema / properties / target / description
      Added value: +"Aria target name from config; default when omitted."
  3. Changed1 schema field changedv1.5.38
    • addedInput schema / properties / confirmed
      Added value: +{
+  "default": false,
+  "title": "Confirmed",
+  "type": "boolean"
+}
  4. Addedv1.5.29
  5. Removedv1.5.28
  6. Addedv1.5.18

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already signal destructive (destructiveHint=true, readOnlyHint=false), but the description goes further: it states irreversibility, that active alerts are unaffected, that confirm=False previews and deletes nothing, and that confirm=True is refused when the definition cannot be read. This adds meaningful behavioral context beyond the annotations and schema.

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 dense and front-loaded: the destructive action, irreversibility, and alternative tool appear early. Every sentence contributes operational guidance or safety context. The final sentence, 'Refused with confirm=True: a definition that cannot be read,' is terse and slightly cryptic, but the overall structure remains efficient.

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 destructive tool with no output schema, the description covers the essential context: irreversibility, effect on active alerts, the preview/confirm workflow, the user-consent requirement, the safer alternative, and the refusal edge case. It also enumerates what blast_radius contains, so an agent understands the preview output without an output schema.

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?

Schema description coverage is 100%, so a baseline of 3 is appropriate. The description adds valuable semantics for confirm: it clarifies the preview-vs-apply difference and the user-consent requirement. It also indicates definition_id comes from list_alert_definitions, though the schema already says that. It does not elaborate on target or confirmed, but the schema descriptions adequately handle those.

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: 'Permanently delete an alert definition.' It clearly distinguishes itself from the sibling set_alert_definition_state by explicitly recommending that alternative for silencing a definition the user may want back. This makes the tool's unique purpose immediately identifiable.

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 and when-not-to-use guidance: use set_alert_definition_state(enabled=False) instead if the definition may be needed later. It also provides a strict operational protocol: without confirm=True only preview, show the blast radius to the user, get explicit decision, and do not confirm on the user's earlier request alone.

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