Skip to main content
Glama
matt-coppinger

Horizon MCP Server

by matt-coppinger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

desktop_pool_action

DestructiveIdempotent

Enable or disable desktop pools and manage VM provisioning to control new user sessions or pause scale-out during maintenance.

Instructions

Enable, disable, or toggle provisioning for one or more desktop pools.

enable/disable controls whether new user sessions can be established. enable-provisioning/disable-provisioning controls whether new VMs are provisioned. Disabling provisioning is the correct way to pause scale-out during maintenance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesenable: allow new sessions. disable: prevent new sessions (existing sessions continue). enable-provisioning: resume VM provisioning. disable-provisioning: pause VM provisioning — use during maintenance windows.
confirmNoOnly used when the server runs with HORIZON_CONFIRMATION=flag (clients without elicitation). Otherwise the user is asked to confirm directly in the client.
pool_idsYesList of desktop pool IDs to act on

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • addedInput schema / properties / confirm
      Added value: +{
+  "default": false,
+  "description": "Only used when the server runs with HORIZON_CONFIRMATION=flag (clients without elicitation). Otherwise the user is asked to confirm directly in the client.",
+  "type": "boolean"
+}
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety bar is partly covered. The description adds real behavioral nuance beyond that: disabling sessions leaves existing sessions running, and provisioning vs. session control are separate concerns. It does not mention the confirmation flow, slighting an otherwise solid disclosure.

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?

Four tightly scoped sentences, front-loaded with the high-level action list before the per-action semantics. Every sentence earns its place, with no filler.

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?

An output schema exists and annotations cover the mutation profile, so the description need not explain returns. It covers the action semantics well but omits the confirm-parameter behavior and batch semantics for multiple pool_ids, minor gaps for a multi-target action tool.

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%, including a fully documented enum for action, so the schema already carries the parameter semantics. The description largely restates the action semantics rather than adding format or syntax beyond the schema, matching the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb (enable/disable/toggle) and resource (provisioning for desktop pools), and clarifies the two distinct control surfaces: session admission versus VM provisioning. It is clear, though it does not explicitly differentiate itself from the sibling update_desktop_pool tool.

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 clear per-action context for when to use each mode, and explicitly states that disabling provisioning is the correct way to pause scale-out during maintenance. It stops short of naming an alternative tool or stating exclusions.

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