Skip to main content
Glama
vmware-skills

vmware-aria

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_report

Destructive

Permanently remove a generated report artifact from Aria Operations. Preview the blast radius first to confirm the exact report before irreversible deletion; the definition and schedules remain intact.

Instructions

[WRITE] Permanently delete a generated report artifact from Aria Operations. Removes only the generated report instance and its output — the report definition and any schedules remain intact; re-run generate_report to recreate it. Deletion is irreversible and is recorded in the audit log. Returns an error if the report_id does not exist; use list_reports to find valid UUIDs first.

Without confirm=True this only previews: it returns blast_radius (report id, title, status, definition id, completion time, owner) 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 report whose status or definition 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.
report_idYesThe report UUID to delete (from generate_report or list_reports).

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 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"
  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 / report_id / description
      Added value: +"The report UUID to delete (from generate_report or list_reports)."
    • 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.9/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true), the description discloses irreversibility, audit logging, error behavior for missing report_id, preview behavior with blast_radius fields, and refusal when a report's status or definition cannot be read. These are substantive behavioral details not available from annotations or schema alone.

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?

The description is front-loaded with the core action and scope, then adds preview/consent and refusal behavior in tight, purposeful follow-ups. Every sentence contributes critical safety or operational information; the length is justified for a destructive tool.

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 is complete: prerequisites, preview return fields, error/refusal behavior, irreversibility, audit logging, and the recreate path are all covered. An agent has everything needed to invoke it safely and correctly.

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 the baseline is 3. The description adds meaningful context for confirm and report_id: preview semantics, the user-consent requirement, 'find valid UUIDs first' via list_reports, and refusal conditions. It adds little for target and confirmed, but those are already well covered by 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 leads with a specific verb and resource: 'Permanently delete a generated report artifact from Aria Operations.' It immediately scopes what is and is not deleted: 'the report definition and any schedules remain intact,' which clearly differentiates it from sibling tools like generate_report, list_reports, and delete_alert_definition.

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: call list_reports first to find valid UUIDs, preview via confirm=False, and get explicit user consent before setting confirm=True. It also states the recovery path ('re-run generate_report to recreate it') and explicitly tells the agent not to set confirm=True on its own because the user hasn't seen what will be deleted.

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