Horizon MCP Server

list_rdsh_farms

Read-only

List all Remote Desktop Session Host (RDSH) farms in a Horizon environment to inventory VDI infrastructure and support management tasks.

Instructions

List all RDS (Remote Desktop Session Host) farms in the environment.

Returns {items, count, page, size, pages_fetched, has_more, next_page, truncated}. If has_more is true there may be more results: call again with page=next_page (or narrow the filter), or pass fetch_all=true to fetch pages automatically (stops after 10 pages or 5000 items and sets truncated=true). Never treat a result with has_more=true as the complete list.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number (1-based)
`size`	No	Results per page (max 1000)
`filter`	No	Horizon filter JSON string
`fetch_all`	No	Fetch successive pages automatically (up to 10 pages / 5000 items). Prefer a filter when you only need a subset.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.2.0Sep 30, 2026

addedInput schema / properties / fetch_all

Added value: +{
+  "default": false,
+  "description": "Fetch successive pages automatically (up to 10 pages / 5000 items). Prefer a filter when you only need a subset.",
+  "type": "boolean"
+}

addedOutput schema / additionalProperties
```
Added value: +true
```

removedOutput schema / properties

Removed value: -{
-  "result": {
-    "items": {},
-    "type": "array"
-  }
-}

removedOutput schema / required
```
Removed value: -[
-  "result"
-]
```
removedOutput schema / x-fastmcp-wrap-result
```
Removed value: -true
```

First observedv0.1.0Sep 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already establish read-only and non-open-world safety, so the bar is lower, and the description still adds meaningful pagination behavior: the fetch_all cap of 10 pages / 5000 items and the truncated flag. It does not cover auth or rate limits, but the pagination disclosure is genuinely valuable beyond the annotations.

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?

Front-loaded with the verb and resource, and the pagination guidance is appropriately dense. The explicit field list {items, count, page, size, ...} duplicates the output schema and is the one redundant segment.

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?

An output schema and full schema coverage exist, so return-value detail is largely redundant, yet the description supplies the pagination contract an agent actually needs to call this correctly. Nothing essential is missing for a read-only list 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%, so the baseline is 3. The description restates fetch_all's behavior (10 pages / 5000 items) and page=next_page, which the schema already documents, adding little new meaning for the four 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 (List) plus a precise resource (RDS / Remote Desktop Session Host farms), and even expands the acronym. It is plainly distinguishable from the singular sibling get_rdsh_farm without needing to open a 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 clear operational guidance for following pagination (page=next_page, narrow the filter, or fetch_all=true) and a strong 'never treat has_more=true as complete' rule. It does not explicitly compare itself to sibling list/get tools, so it falls short of the top tier.

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

Deploy Server