Skip to main content
Glama
vmware-skills

vmware-vdi

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

machine_maintenance

Idempotent

Toggle maintenance mode for VDI machines, previewing affected users and sessions before applying changes.

Instructions

[WRITE] Enter (enabled=True) or exit (False) maintenance mode for machine(s).

Maintenance drains the machine (no new sessions). A bare call returns blast_radius (machine ids, states, assigned users) and changes nothing; confirm=True applies. 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. 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 applies it.
enabledYesTrue enters maintenance; False exits.
machine_idsYesMachine ids (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 applies."New value: +"False (default) returns the blast radius and changes nothing. True applies it."
  2. Changed5 schema fields changedv1.1.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / confirm / description
      Added value: +"False previews; True applies."
    • addedInput schema / properties / enabled / description
      Added value: +"True enters maintenance; False exits."
    • addedInput schema / properties / machine_ids / description
      Added value: +"Machine ids (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.4/5.0
Behavior5/5

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

Beyond the annotations, it discloses the two-phase behavior, the exact contents of blast_radius, that a bare call changes nothing, that unreadable machines are refused, and that the operation is audited. This aligns with readOnlyHint=false and idempotentHint=true rather than contradicting them.

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 first sentence front-loads the core action, and each following sentence carries essential operational or safety information. There is no filler or repetition; the length is appropriate for a two-phase mutation with significant safety implications.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description does explain the blast_radius return value for the read-only first call, plus refusal and audit behavior. A minor gap remains: what the caller should expect after confirm=True applies is not described, and the fate of existing sessions is only implied by 'no new sessions.'

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%, so the baseline is 3. The description restates the enabled and confirm semantics already present in the schema and adds a safety policy, but it does not materially expand parameter meanings beyond what the input schema documents.

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-resource pair: 'Enter (enabled=True) or exit (False) maintenance mode for machine(s).' It also clarifies the operational effect, 'Maintenance drains the machine (no new sessions),' which distinguishes this from sibling machine mutators like machine_reset or machine_remove.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit procedural guidance: call without confirm to inspect blast_radius, show the user, wait for their decision, and never auto-confirm before the user has seen the blast radius. It does not explicitly list when-not-to-use or name alternative tools, so it stops short of a 5.

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