Horizon MCP Server

delete_desktop_pool

Delete a desktop pool and all its machines, terminating active user sessions. Irreversible, so require explicit confirmation before freeing VDI resources.

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	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.
`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.

First observedv0.1.0Sep 10, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It clearly states the operation is destructive, deletes all machines, terminates active sessions, and mandates confirmation. This fully informs the agent of the consequences before invocation.

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 concise sentences: the first gives the core action, the second (CAUTION) front-loads critical safety information. No filler; every sentence earns its place.

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 operation with no annotations, the description completely covers what it does, its effects, and the required pre-checks and user consent. An agent has everything needed to decide and correctly invoke the 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%, and the 'confirm' parameter description already provides detailed guidance (must be true, pre-calls, user approval). The tool description adds no extra parameter meaning beyond reinforcing confirmation, so the baseline of 3 is appropriate.

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 its scope ('all of its machines'). This clearly differentiates from sibling read/update tools like get_desktop_pool and update_desktop_pool.

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?

Explicitly warns of irreversibility and requires user confirmation. The parameter description on 'confirm' goes further, instructing the agent to call get_desktop_pool and list_sessions to verify safety before proceeding. This gives clear when-to-use and prerequisites, and implicitly when not to use (without approval).

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

Install Server