Horizon MCP Server

create_rdsh_farm

Create a new RDS farm for Horizon VDI. Configure automated or manual farms, linking to RDS desktop pools. Note: automated farms start provisioning VMs immediately.

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

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

A3.6/5.0

Behavior3/5

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

No annotations are present, so the description carries the full behavioral burden. It does disclose a critical side effect: provisioning an AUTOMATED farm immediately begins creating VMs in vCenter, and it instructs to confirm with the user. Still, it omits other behavioral details such as permissions, error cases, reversibility, or what happens on a MANUAL farm.

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 only two sentences with no filler. The action is stated first, and the critical safety caution is immediate and prominent. 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?

For a create tool with a nested spec, the schema supplies detailed parameter guidance and the output schema covers return values. The description adds the crucial safety context about immediate VM creation. It is largely complete, though it could be stronger by explicitly noting MANUAL vs AUTOMATED behavior beyond the warning and by routing to alternatives.

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%, so the schema carries the parameter detail. The spec field's description is notably rich: it lists required keys, AUTOMATED provisioning fields, the desktop_id link, and the lookup tools for resolving IDs. The top-level description adds no additional parameter semantics, warranting the baseline score 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 and resource: 'Create a new RDS farm.' This clearly identifies the operation and distinguishes it at a basic level from sibling create tools like create_desktop_pool or create_application_pool. It does not explicitly contrast itself with those siblings, so it falls short of a 5.

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?

The CAUTION gives a meaningful prerequisite: confirm with the user before calling, and warns about the immediate side effects for AUTOMATED farms. However, it does not explicitly state when this tool should be used instead of alternatives, nor does it provide exclusions or comparison guidance.

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

Deploy Server