Skip to main content
Glama
vmware-skills

vmware-aria

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

start_resource_maintenance

Idempotent

Place a VMware resource into maintenance to stop monitoring and alerting during planned work. Preview blast radius first, then confirm to apply, optionally with a timed window for automatic recovery.

Instructions

[WRITE] Put one resource in maintenance so Aria stops alerting on it and collecting its data — use before planned work such as powering a VM or host off.

Pass duration_minutes OR end_time_ms for a timed window (state MAINTAINED; the resource returns to its prior state when it expires). Pass neither for manual maintenance (MAINTAINED_MANUAL) that lasts until end_resource_maintenance — easy to forget, so prefer a window.

Without confirm=True this only previews: it reads the resource and returns blast_radius (resource name and kind, each adapter's state, whether it is in maintenance now, and the requested window) 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. Refused with confirm=True: a resource already in maintenance (starting again would replace that window) and a resource whose state cannot be read.

Acting returns the state before and after, confirmed (true / false / null when the after-state could not be read — null is unknown, not failure) and a note. Undo: end_resource_maintenance, recorded only when the resource was known not to be in maintenance before.

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.
end_time_msNoWindow end as epoch MILLISECONDS in the future. Not with duration_minutes.
resource_idYesResource UUID from list_resources (not the resource name).
duration_minutesNoWindow length in whole minutes, 1-525600. Not with end_time_ms.

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 start maintenance. 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. Addedv1.15.0

TDQS

A5/5.0
Behavior5/5

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

The description discloses much more than annotations alone: preview vs apply mode, refusal conditions (already in maintenance, unreadable state), the meaning of returned confirmed value (null unknown, not failure), and condition for undo recording. There is no contradiction with annotations: readOnlyHint=false matches the write nature, destructiveHint=false matches maintenance being non-destructive, and idempotentHint is consistent with repeated starts being refused rather than replacing the window.

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 long but efficient: it front-loads the write nature and purpose, then uses short labeled sections for windows, confirmation, refusals, and output. Every sentence earns its place by either shaping the invocation or protecting against mistakes.

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 state-changing tool with no output schema, it covers the preview/confirm safety workflow, timed vs manual windows, refusal cases, return semantics, and undo. The remaining parameter details (target, confirmed alias) are fully documented in the input schema, so nothing an agent needs for first call is missing.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds real semantics: duration_minutes and end_time_ms are framed as mutually exclusive window options, passing neither means manual maintenance, and confirm=False vs True determines preview vs apply. It also warns against setting confirm=True autonomously, which the schema alone 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?

The description names a specific operation ('Put one resource in maintenance'), the concrete effect ('Aria stops alerting on it and collecting its data'), and the intended context ('before planned work such as powering a VM or host off'). It also distinguishes itself from the sibling undo tool by explicitly naming end_resource_maintenance as the way to end maintenance.

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 clear when-to-use context ('before planned work'), explicit choices between timed and manual maintenance, and a strong workflow rule: without confirm=True it only previews and must be shown to the user before setting confirm=True. It also states refusal cases and names end_resource_maintenance as the undo path. This goes beyond a vague hint and gives actionable decision rules.

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