Horizon MCP Server

create_rdsh_farm

Creates a new RDS farm in Horizon, provisioning VMs for automated farms if configured; confirm before starting automated provisioning.

Instructions

Create a new RDS farm.

CAUTION: Provisioning an AUTOMATED farm immediately begins creating VMs in vCenter. Always confirm with the user before calling this.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`spec`	Yes	Full farm specification, verified live against a real Horizon server (2606). Required top-level keys: name, type (AUTOMATED \| MANUAL), access_group_id (from the horizon://config/local-access-groups resource). AUTOMATED farms require an automated_farm_settings object — NOT the same shape as create_desktop_pool's provisioning_settings, and nested one level deeper — containing: vcenter_id (list_virtual_centers), max_session_type (LIMITED \| UNLIMITED — max_sessions is required when LIMITED); provisioning_settings: {parent_vm_id (list_base_vms), base_snapshot_id (list_base_vm_snapshots), datacenter_id (list_datacenters), vm_folder_id (list_vm_folders), host_or_cluster_id (list_hosts_or_clusters), resource_pool_id (list_resource_pools)}; storage_settings: {datastores: [{datastore_id}]} (list_datastores); customization_settings: {instant_clone_domain_account_id (list_ic_domain_accounts), ad_container_rdn (list_ad_domains + list_ad_containers)}; pattern_naming_settings: {naming_pattern, max_number_of_rds_servers}. settings.desktop_id links the farm to its RDS desktop pool.

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 / spec / description

Previous value: -"Full farm specification. Required keys: name, type (AUTOMATED | MANUAL), source (INSTANT_CLONE | RDS). AUTOMATED farms also require provisioning_settings with the same fields as create_desktop_pool (virtual_center_id, parent_vm_id, snapshot_id, datacenter_id, vm_folder_id, host_or_cluster_id, resource_pool_id, datastores, nics, naming_pattern, max_machine_count). settings.desktop_id links the farm to its RDS desktop pool. Use list_virtual_centers, list_base_vms, list_base_vm_snapshots, list_datacenters, list_vm_folders, list_hosts_or_clusters, list_datastores, list_resource_pools, and list_network_labels to look up all required IDs."New value: +"Full farm specification, verified live against a real Horizon server (2606). Required top-level keys: name, type (AUTOMATED | MANUAL), access_group_id (from the horizon://config/local-access-groups resource). AUTOMATED farms require an automated_farm_settings object — NOT the same shape as create_desktop_pool's provisioning_settings, and nested one level deeper — containing: vcenter_id (list_virtual_centers), max_session_type (LIMITED | UNLIMITED — max_sessions is required when LIMITED); provisioning_settings: {parent_vm_id (list_base_vms), base_snapshot_id (list_base_vm_snapshots), datacenter_id (list_datacenters), vm_folder_id (list_vm_folders), host_or_cluster_id (list_hosts_or_clusters), resource_pool_id (list_resource_pools)}; storage_settings: {datastores: [{datastore_id}]} (list_datastores); customization_settings: {instant_clone_domain_account_id (list_ic_domain_accounts), ad_container_rdn (list_ad_domains + list_ad_containers)}; pattern_naming_settings: {naming_pattern, max_number_of_rds_servers}. settings.desktop_id links the farm to its RDS desktop pool."

First observedv0.1.0Sep 10, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations only declare the generic non-read-only/non-destructive flags. The description adds genuinely useful behavioral context: an AUTOMATED farm immediately begins creating VMs in vCenter and should be user-confirmed first — a side effect the flags alone do not convey. It says nothing about permissions or failure/rollback behavior, keeping it below 5.

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 blocks: the purpose is front-loaded, and the caution follows with no filler or redundancy. Every sentence earns its place.

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?

A create operation whose full spec is exhaustively documented in the schema, with an output schema present so return values need no description. The description supplies the critical side-effect caveat. Minor gap: no mention of the login/prerequisite context, though siblings cover that.

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 single `spec` parameter is documented in exceptional depth inside the schema, including required keys, enum values, and pointer tools (list_base_vms, list_datacenters, etc.). The description adds no parameter meaning beyond that, so the baseline 3 for full schema coverage applies.

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+resource ("Create a new RDS farm") that an agent can distinguish from create_desktop_pool and the other create_* siblings by resource type. It stops short of explicitly differentiating itself from siblings like update_rdsh_farm or delete_rdsh_farm, so it does not reach the top band.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the verb and reinforced by the warning to confirm with the user before provisioning an AUTOMATED farm, which is a real precondition. However, it never names alternatives (e.g., create_desktop_pool vs. this) or states when a farm is the right choice over a pool, leaving the routing decision to inference.

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

Deploy Server