Skip to main content
Glama

vmware_list_vms

Read-onlyIdempotent

List vCenter VMs with optional filters for name and power state, with pagination support. Results returned as a markdown table or JSON.

Instructions

Lists the vCenter VMs with filters and pagination.

In json: {total, count, offset, has_more, next_offset, vms:[{name, moid, power_state, guest_os, ip, hostname, cpu, memory_mb, host, vmware_tools}]}. In markdown: table.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results
offsetNoPagination offset
name_filterNoSubstring to search for in the name (case-insensitive)
power_stateNoState filter: poweredOn, poweredOff or suspended
response_formatNomarkdown (default, compact table) or json (full structure)markdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive. The description adds details about pagination (has_more, next_offset) and output formats, exceeding baseline annotation coverage.

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?

Extremely concise: two sentences. First sentence states purpose, second explains output structure in both formats. No redundancy, front-loaded with key information.

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?

Given the tool's simplicity and rich annotations/schema, the description covers purpose, output structure, and key features (filters, pagination). Lacks usage context but otherwise adequate.

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 coverage is 100%, so parameters are well-documented. The description mentions filters and pagination but doesn't add new semantic meaning beyond the schema, meeting baseline.

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 clearly states it lists VMs with filters and pagination, which is specific. It distinguishes from sibling tools like vmware_get_vm (single VM) implicitly but not explicitly.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives such as vmware_get_vm or vmware_list_hosts. The description lacks any context about selection criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Hokonoken/mcp-vmware'

If you have feedback or need assistance with the MCP directory API, please join our Discord server