Skip to main content
Glama
vmware-skills

vmware-vdi

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

entitlement_remove

DestructiveIdempotent

Revoke desktop-pool access from AD user/group SIDs. Displays the blast radius of affected principals before applying changes.

Instructions

[WRITE] Revoke desktop-pool access from AD user/group SID(s).

Get SIDs from entitlement_list. A bare call returns blast_radius (pool identity, which principals lose access and which were not entitled) and revokes nothing; confirm=True revokes. Refused when the pool's current entitlements cannot be read. 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 revokes.
pool_idYesThe desktop-pool id (from pool_list).
ad_user_or_group_idsYesAD SIDs to remove (from entitlement_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 revokes."New value: +"False (default) returns the blast radius and changes nothing. True revokes."
  2. Changed5 schema fields changedv1.1.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / ad_user_or_group_ids / description
      Added value: +"AD SIDs to remove (from entitlement_list)."
    • addedInput schema / properties / confirm / description
      Added value: +"False previews; True revokes."
    • addedInput schema / properties / pool_id / description
      Added value: +"The desktop-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.8/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint, readOnlyHint:false), the description discloses the critical two-phase behavior, the no-op bare call, the refusal condition when entitlements cannot be read, and that calls are audited. This gives an agent the safety context it needs.

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 well structured: it leads with the core action, then the two-phase workflow, refusal condition, and safety instruction. Every sentence contributes necessary information without filler.

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 destructive, two-phase tool with no output schema, the description is complete: it explains the blast_radius return, how to confirm, when it refuses, what inputs to use, and the required user-decision loop. Nothing necessary for correct and safe invocation 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 already 100%, and the description adds important semantics: ad_user_or_group_ids must come from entitlement_list, pool_id from pool_list, and confirm's default false versus true behavior is explicitly tied to blast_radius and revocation. The description adds meaning beyond the schema definitions.

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?

States a specific verb and resource: 'Revoke desktop-pool access from AD user/group SID(s).' The two-phase behavior (bare call returns blast radius, confirm=True revokes) further clarifies exactly what the tool accomplishes, and the instruction to get SIDs from entitlement_list distinguishes it from sibling tools.

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?

Gives clear context for safe use: show blast_radius to the user and wait for their decision, and never set confirm=True unilaterally. It also names the source tool for SIDs (entitlement_list), though it does not explicitly discuss alternatives such as entitlement_add for granting access.

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