Skip to main content
Glama
vmware-skills

vmware-vdi

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

pool_set_enabled

Idempotent

Disable a desktop pool to block new sessions while existing ones continue, or re-enable it. Preview the impact first, then confirm to apply changes safely.

Instructions

[WRITE] Enable or disable a desktop pool — disabling stops NEW sessions (existing keep running).

Idempotent (matching state returns a noop). A bare call returns blast_radius (pool identity, current and new enabled state) and changes nothing; confirm=True applies. A pool whose current enabled 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 enables; False disables.
pool_idYesThe pool id (from pool_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 enables; False disables."
    • addedInput schema / properties / pool_id / description
      Added value: +"The pool id (from pool_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.9/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, idempotent=true), the description discloses the confirmation workflow, idempotent noop behavior, refusal when current state cannot be read, and the audited nature of the call. This is exactly the behavioral context an agent needs for a mutation with side effects.

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 effect, and every subsequent sentence earns its place: idempotency, blast_radius workflow, refusal condition, and user-consent rule. It is information-dense without redundancy.

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 mutating tool with no output schema, the description covers the return contract (blast_radius contents), the confirmation semantics, the failure case (cannot read current state), and the safety requirement of user consent. This is complete enough for an agent to invoke it 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 schema already documents target, confirm, enabled, and pool_id. The description adds meaningful semantics for confirm (bare call returns blast_radius and changes nothing; True applies it), and clarifies the enabled effect, which goes slightly beyond the schema's one-line descriptions.

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 '[WRITE] Enable or disable a desktop pool' and clearly states the behavioral scope ('disabling stops NEW sessions (existing keep running)'). This distinguishes it from sibling pool_list/pool_get/pool_push_image and leaves no ambiguity about what the tool does.

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 operational guidance: a bare call only returns blast_radius, confirm=True applies the change, and the agent must 'Show blast_radius to the user and wait for their decision.' It even states a when-not ('Do not set confirm=True on your own because the user asked for this earlier'), which is more actionable than a generic alternative comparison.

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