Skip to main content
Glama

vmware_host_vibs

Read-onlyIdempotent

List software packages (VIBs) installed on a VMware ESXi host, with filtering by name and pagination support. Returns results in table or JSON format.

Instructions

Software packages (VIBs) installed on a host (equivalent of esxcli software vib list) and image profile.

In json: {host, image_profile, total, count, offset, has_more, next_offset, vibs:[{name, version, vendor, acceptance_level}]}. In markdown: table.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostYesName of the ESXi host
limitNoMaximum number of results
offsetNoPagination offset
name_filterNoSubstring to search for in the VIB name
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 declare readOnlyHint, idempotentHint, destructiveHint. Description adds details about pagination, output formats (JSON/markdown), and the structure of results, providing useful context beyond 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?

Description is two sentences plus a JSON example. It is front-loaded with purpose and format. The JSON structure is lengthy but informative; overall efficient.

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 5 parameters with filters and pagination, the description details output fields and format. No formal output schema but the provided JSON structure compensates. Adequate for the tool's complexity.

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 covers all 5 parameters with descriptions. The description adds minimal extra value by outlining the response structure but does not enhance parameter understanding beyond the schema's detail.

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?

Description clearly states the tool lists VIBs and image profile on a host, with a specific verb 'list' and resource 'VIBs'. It distinguishes from sibling tools like vmware_host_health by focusing on software packages.

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 explicit guidance on when to use this tool versus alternatives. It mentions equivalence to 'esxcli software vib list' but does not compare with other host tools in the sibling list.

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