Skip to main content
Glama

end_resource_maintenance

Idempotent

End a VMware Aria resource's maintenance mode so alerting and data collection resume. Preview the blast radius first; confirm only after user approval.

Instructions

[WRITE] Take one resource out of maintenance so Aria resumes alerting on it and collecting its data.

Without confirm=True this only previews: it reads the resource and returns blast_radius (resource name and kind, each adapter's state, the maintenance mode it is in) 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 known not to be in maintenance (an adapter reports a state such as STARTED or STOPPED — nothing to end), and a resource whose state is unknown (unreadable, or reported as UNKNOWN / NONE) — end that one from the Aria UI or the CLI after checking it.

Acting returns the state before and after, confirmed (true / false / null when unknown) and a note. Undo: start_resource_maintenance (re-enters as manual maintenance), recorded only when the resource was known to be in maintenance before.

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": {
      "resource_id": "<resource_id>"
    },
    "name": "end_resource_maintenance"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetNoAria target name from config; default when omitted.
confirmNoFalse (default) returns the blast radius and changes nothing. True applies it.
resource_idYesResource UUID from list_resources (not the resource name).

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. 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 end 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"
  3. Addedv1.15.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false, idempotentHint=true, destructiveHint=false; the description goes well beyond by describing the preview payload (blast_radius with resource name/kind, adapter states, maintenance mode), the return shape (before/after state, confirmed true/false/null, note), and the undo path via start_resource_maintenance. It also adds a crucial agent-behavior constraint: do not set confirm=True on the user's earlier request alone.

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 write marker and the core action, then structured into preview, refusal, return, and undo paragraphs with no filler. It is longer than typical but nearly every clause carries operational information; the preview sentence repeats slightly when describing 'changes nothing' twice.

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?

There is no output schema, so the description carries the return contract itself and does so precisely, including the nullable confirmed field. Combined with refusal cases, undo, and preview semantics, an agent has everything needed to call this correctly on a mutating, open-world tool.

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 earns above that by explaining the real consequence of confirm (preview versus apply) and explicitly cautioning against self-authorizing it, which the schema text does not convey. resource_id and target semantics remain entirely schema-side.

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?

Opens with a bracketed [WRITE] marker and a specific verb+resource: 'Take one resource out of maintenance so Aria resumes alerting on it and collecting its data.' The inverse sibling start_resource_maintenance is named later, so an agent can distinguish the pair 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?

States the two-phase flow explicitly: without confirm=True it only previews, with confirm=True it applies. It also names the exact conditions that produce refusals (adapter already STARTED/STOPPED, or state UNKNOWN/NONE) and routes those cases to the Aria UI or CLI, which is a genuine alternative.

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