mcp-vmware

Overview Schema Source Related Servers Discussions Admin

vmware_host_advanced_settings

Read-onlyIdempotent

Retrieve advanced ESXi host settings filtered by a key prefix (e.g., Net., Mem., NFS.) to inspect or prepare for modification.

Instructions

Advanced settings of a host (equivalent of esxcli system settings advanced list), filtered by key prefix.

Returns a structured object {host, filter, count, settings:[{key, value}]}. Modify with vmware_host_set_advanced_setting (host.config).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "host": "<host>",
      "filter_prefix": "<filter_prefix>"
    },
    "name": "vmware_host_advanced_settings"
  }
}

Input Schema

Name	Required	Description	Default
`host`	Yes	Name of the ESXi host
`filter_prefix`	Yes	Key prefix, e.g. Net., Mem., NFS., UserVars. (required, >1000 settings)

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 14, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. Description adds value by specifying the return structure and equivalent esxcli command, confirming it's a safe read operation.

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 sentences, each serving a purpose: purpose, return structure, modification alternative. No redundancy and easy to parse.

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?

Given high schema coverage, rich annotations, and output schema implied, the description is complete. It covers reading, filtering, output format, and modification, making it fully actionable.

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 covers both parameters fully, but description adds examples of prefix values and notes the large number of settings, aiding selection. This exceeds mere schema repetition.

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 it lists advanced settings of a host, equivalent to a specific esxcli command, with key prefix filtering. It distinguishes from sibling tools by specifying its focus on advanced settings, not other host configuration areas.

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?

Provides clear context: it lists settings filtered by prefix and mentions the modification counterpart. However, it does not explicitly exclude scenarios or provide when-not-to-use guidance relative to siblings.

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