Horizon MCP Server

delete_desktop_pool

Destructive

Permanently delete a desktop pool and all its machines via the Horizon REST API. Terminates active user sessions, so confirm affected pools and sessions before calling.

Instructions

Delete a desktop pool and all of its machines.

CAUTION: This is irreversible. All machines in the pool are deleted and any active user sessions are terminated. Always confirm with the user before calling this.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`confirm`	No	Only used when the server runs with HORIZON_CONFIRMATION=flag (clients without elicitation). Otherwise the user is asked to confirm directly in the client. Before deleting, call get_desktop_pool and list_sessions (filtered by desktop_pool_id) so you can tell the user what will be affected.
`pool_id`	Yes	Desktop pool ID — obtain from list_desktop_pools

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.2.0Sep 30, 2026

changedInput schema / properties / confirm / description

Previous value: -"Must be explicitly True to proceed. Before setting this, call get_desktop_pool and list_sessions (filtered by desktop_pool_id) to verify the pool is safe to delete, then obtain explicit user approval."New value: +"Only used when the server runs with HORIZON_CONFIRMATION=flag (clients without elicitation). Otherwise the user is asked to confirm directly in the client. Before deleting, call get_desktop_pool and list_sessions (filtered by desktop_pool_id) so you can tell the user what will be affected."

First observedv0.1.0Sep 10, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true and non-idempotent, but the description adds the crucial facts the annotations cannot convey: the operation is irreversible, all machines go, and active user sessions are terminated. That is exactly the extra context an agent needs before a destructive call.

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?

Two short parts: the action with scope first, then a front-loaded CAUTION that earns every word. No filler, no 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 destructive mutation tool with an output schema already present, the description covers purpose, irreversibility, affected entities, and the confirmation obligation. Nothing an agent needs to decide and call safely 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 itself documents pool_id source and the confirm/HORIZON_CONFIRMATION semantics in detail, so the description need not repeat it. Baseline 3 applies since the description adds nothing beyond the schema for parameters.

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 (delete) and resource (desktop pool) plus the blast radius ('and all of its machines'). It is clearly distinguishable from siblings like delete_rdsh_farm and delete_application_pool without opening any schema.

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 explicit when-to-use guidance by mandating user confirmation before calling, and the schema reinforces this with the get_desktop_pool/list_sessions pre-check. It does not name a direct alternative, but none is really needed for a terminal delete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server