mcp-vmware

Overview Schema Source Related Servers Discussions Admin

vmware_host_network_config

Read-onlyIdempotent

Retrieve network configuration of an ESXi host, including vSwitches, portgroups, vmkernel interfaces, and physical NICs.

Instructions

Network configuration of a host (equivalent of esxcli network): vSwitches, portgroups, vmkernel interfaces, physical NICs.

Returns a structured object {host, vswitches:[...], portgroups:[...], vmkernel_nics:[...], physical_nics:[...]}.

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>"
    },
    "name": "vmware_host_network_config"
  }
}

Input Schema

Name	Required	Description	Default
`host`	Yes	Name of the ESXi host

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 14, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's job is to add context. It does so by detailing the return structure, though it does not cover auth needs or rate limits. The description adds value without contradicting annotations.

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?

Two efficient sentences: first defines scope, second details return structure. No wasted words, and it's front-loaded.

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?

With one parameter, full schema coverage, clear annotations, and an output schema, the description sufficiently covers the tool's purpose and output. No additional context is needed for a read-only network config retrieval tool.

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% for the single parameter 'host', and the description does not add further semantic detail beyond what the schema provides. Baseline 3 is appropriate.

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 retrieves network configuration of a host, analogous to esxcli network, and enumerates components (vSwitches, portgroups, vmkernel interfaces, physical NICs). This distinguishes it from sibling tools like vmware_list_networks or vmware_get_host.

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?

No explicit guidance on when to use this tool vs alternatives. While the scope is clear from the description, it does not provide when-not or alternatives, which is a gap for an agent deciding between multiple host-related tools.

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