Skip to main content
Glama
vmware-skills

vmware-vdi

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

machine_reset

Destructive

Hard-reset desktop machine(s), discarding unsaved state. Preview affected machines and users first, then confirm to execute. Refuses reset when machine state cannot be read.

Instructions

[WRITE] Hard-reset desktop machine(s) — the user loses unsaved state.

A bare call returns blast_radius (machine ids, names, states, assigned users) and resets nothing; confirm=True resets. A machine whose state cannot be read is refused. Show blast_radius to the user and wait for their decision. Do not set confirm=True on your own because the user asked for this earlier: they have not seen the blast radius yet. For a graceful in-guest reboot use vmware-aiops (the vCenter VM). Audited.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNoHorizon target from config.yaml; omit to use the default.
confirmNoFalse (default) returns the blast radius and changes nothing. True resets.
machine_idsYesMachine ids to reset (from machine_list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedInput schema / properties / confirm / description
      Previous value: -"False previews; True resets."New value: +"False (default) returns the blast radius and changes nothing. True resets."
  2. Changed4 schema fields changedv1.1.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / confirm / description
      Added value: +"False previews; True resets."
    • addedInput schema / properties / machine_ids / description
      Added value: +"Machine ids to reset (from machine_list)."
    • addedInput schema / properties / target / description
      Added value: +"Horizon target from config.yaml; omit to use the default."
  3. First observedv1.0.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark this as destructive and non-read-only, but the description adds substantial context beyond that: the two-phase confirm behavior, the refusal to reset machines whose state cannot be read, the expectation to show blast_radius to the user, the warning not to self-confirm, and the 'Audited' note. This gives the agent a clear mental model of the tool's safety envelope.

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?

Every sentence earns its place: core operation first, then the two-phase workflow, then the user-consent warning, then the alternative tool. Densely informative with no filler or repetition of schema content, and the most safety-critical guidance is front-loaded.

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?

The description fully equips an agent to call this tool correctly despite the absence of an output schema: it explains exactly what a bare call returns (blast_radius with machine ids, names, states, assigned users), how confirmation works, what can cause refusal, and when to route to a different tool. Nothing critical is missing.

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

Parameters3/5

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

Schema description coverage is 100%, and the schema already explains confirm's false/true semantics, machine_ids source, and target default. The description reinforces the confirm behavior but does not add new parameter-level meaning beyond what the schema provides. Baseline 3 is appropriate.

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 opens with a specific verb and resource: 'Hard-reset desktop machine(s)' and immediately states the consequence ('user loses unsaved state'). This clearly distinguishes it from siblings like machine_remove or machine_maintenance, and the explicit contrast with vmware-aiops further disambiguates it from graceful reboot operations.

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 workflow instructions: a bare call returns blast_radius and resets nothing, confirm=True resets, and the agent must show blast_radius and wait for user decision before setting confirm. It also names an alternative tool for graceful reboots (vmware-aiops), making the when-to-use vs when-not-to-use boundary explicit.

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