vmware-vdi

list_desktop_pools

Read-onlyIdempotent

Retrieve Horizon desktop pools with IDs, names, types, enabled status, and assignments. Use paginated results to verify pool state before enabling pools or pushing images.

Instructions

[READ] List Horizon desktop pools: id, name, type (AUTOMATED/MANUAL/RDS), enabled, assignment.

The verify pair for set_desktop_pool_enabled and push_desktop_pool_image. Paginated envelope.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_desktop_pools"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Page size (default 50).
`offset`	No	Page offset.
`target`	No	Horizon target from config.yaml; omit to use the default.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.4.1Oct 21, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, destructive=false, openWorld), so the bar is lower. The description adds meaningful behavioral context by disclosing the 'Paginated envelope' return shape, which the annotations do not convey.

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?

Three tight lines: purpose + fields, then usage, then return shape, all front-loaded with no waste. The '[READ]' tag is redundant with readOnlyHint but negligible.

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 no output schema, the description usefully lists returned fields and notes pagination, and annotations cover the safety profile, so an agent has enough to call it correctly. Slightly more detail on pagination mechanics or default scoping would round it out.

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 limit, offset, and target are already documented in the schema. The description adds no additional parameter meaning beyond what the schema provides, which is the baseline 3 for fully-covered schemas.

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') and resource ('Horizon desktop pools') and enumerates the returned fields (id, name, type, enabled, assignment). It is clearly distinguishable from siblings like list_app_pools and list_vdi_images without opening any 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?

Explicitly identifies its role as 'the verify pair for set_desktop_pool_enabled and push_desktop_pool_image', giving concrete when-to-use context tied to specific sibling mutations. It stops short of naming when NOT to use it versus the other list_* siblings, so it is short of a full 5.

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