Skip to main content
Glama
Sign In
vmware-aria

vmware-aria

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_alert_definition

Destructive

Permanently deletes an alert definition from Aria Operations, showing a blast-radius preview unless confirm is set; 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.

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": {
      "definition_id": "<definition_id>"
    },
    "name": "delete_alert_definition"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetNoAria target name from config; default when omitted.
confirmNoFalse (default) returns the blast radius and changes nothing. True applies it.
definition_idYesAlert definition id to delete (from list_alert_definitions).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.4.2
    • removedInput schema / properties / confirmed
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "boolean"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Deprecated alias for confirm; removed in the next minor release. confirmed=False holds even when confirm=True.",
-  "title": "Confirmed"
-}
  2. 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)."
  3. 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."
  4. Changed1 schema field changedv1.5.38
    • addedInput schema / properties / confirmed
      Added value: +{
+  "default": false,
+  "title": "Confirmed",
+  "type": "boolean"
+}
  5. Addedv1.5.29
  6. Removedv1.5.28
  7. 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 declare destructiveHint=true and readOnlyHint=false, yet the description adds substantial context: irreversibility, the fact that active alerts survive, the confirm-gating behavior, what the preview returns, and the explicit instruction not to self-confirm. This is exactly the value-add beyond annotations the dimension rewards.

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?

Front-loaded with the destructive nature and the alternative, then the confirm mechanics. Each sentence carries information, though the instruction about not confirming on the user's earlier request is slightly verbose and could be tightened.

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?

No output schema exists, and the description compensates by enumerating the preview payload fields (id, name, adapter, resource kind, criticality, state count). For a destructive three-parameter tool, nothing essential is missing.

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 coverage is 100%, so baseline is 3; the description still earns extra credit by explaining the behavioral consequence of confirm (preview with blast_radius contents vs. actual deletion) and the refusal condition for unreadable definitions, which the schema's short label does not convey.

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?

States a specific verb+resource ('Permanently delete an alert definition') plus the scope ('removes the alert definition from Aria Operations') and explicitly contrasts with the sibling set_alert_definition_state. An agent can distinguish it from the list/create/get siblings immediately.

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?

Gives an explicit alternative ('Use set_alert_definition_state(enabled=False) instead to silence a definition you may want back') and the condition selecting it, plus the two-phase preview-then-confirm workflow and the refusal case. When/when-not guidance is unusually complete.

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