Horizon MCP Server

list_desktop_pools

Read-only

Fetches all VDI and RDS desktop-pool entries in an Omnissa Horizon environment, returning counts and pagination metadata so IT staff can review provisioned virtual desktops.

Instructions

List all desktop pools (VDI and RDS) in the Horizon 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. Example: {"type":"Contains","name":"name","value":"dev"} — see Horizon REST API docs for full filter syntax.
`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

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: automatic pagination stops after 10 pages / 5000 items and sets truncated=true, and a has_more=true result must not be treated as complete. It overlaps somewhat with the declared output schema by enumerating the return fields, which slightly dilutes the added value.

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 purpose sentence followed by return contract and a clear pagination warning; every sentence is actionable and the critical 'never treat has_more=true as complete' caution is stated plainly. The enumerated return-field list is mildly redundant given a declared output schema, which keeps this from a 5.

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?

With annotations, a full output schema, and 100% parameter description coverage, the structured fields carry most of the burden and the description fills the remaining pagination/truncation gap well. It stops short of noting session/auth prerequisites or distinguishing this list from the RDSH-farm and application-pool listings, which is the only real hole for a tool with this many lookalike siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so a baseline of 3 is warranted; the description rises above that by explaining how parameters interact with returned fields (has_more -> page=next_page) and by tying fetch_all to its 10-page/5000-item cap and truncated flag. The filter parameter itself is left entirely to the schema and external Horizon REST docs.

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?

States a specific verb and resource ('List all desktop pools') and scopes it to 'VDI and RDS' pools in the Horizon environment, so an agent knows the resource type. It does not, however, differentiate itself from siblings that look similar — get_desktop_pool (single item), list_rdsh_farms, or list_application_pools — so the reader must infer the boundary themselves.

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 description gives strong operational guidance on how to consume results (call again with page=next_page, narrow the filter, or pass fetch_all=true) and explicitly warns not to treat has_more=true as a complete list. It says nothing about when to choose this tool over the sibling listing tools or about prerequisites such as an active Horizon session, so alternative-routing guidance is absent.

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

Deploy Server