mcp-vmware

Overview Schema Source Related Servers Discussions Admin

vmware_list_networks

Read-onlyIdempotent

Retrieve a list of standard and distributed portgroups from VMware vCenter, including name, type, VLAN, and associated VMs.

Instructions

Lists the networks (standard and distributed portgroups).

In json: {total, count, ..., networks:[{name, moid, type, accessible, vms, vlan}]}. vlan is only filled in for distributed portgroups. In markdown: table.

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": "vmware_list_networks"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of results
`offset`	No	Pagination offset
`response_format`	No	markdown (default, compact table) or json (full structure)	markdown

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.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds valuable behavioral context: it describes the output structure in JSON (fields like name, moid, type, accessible, vms, vlan) and notes that 'vlan' is only filled for distributed portgroups. It also explains the difference between JSON and markdown output formats. This goes 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise—two sentences plus a brief sample structure—while conveying the core purpose and key behavioral details. Every sentence earns its place; no wasted words.

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 output schema exists, the description need not detail return values, but it does provide a helpful output skeleton. It covers the main purpose, output format options, and a conditional field (vlan). Minor gap: it does not mention pagination behavior, but the schema covers limit/offset. Overall complete for a list 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 description coverage is 100% (all three parameters are documented in the schema). The description does not add any additional meaning or context for the parameters 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?

The description clearly states the tool lists networks, specifically standard and distributed portgroups. It uses a specific verb ('Lists') and resource ('networks'), and distinguishes itself from sibling list tools like vmware_list_hosts or vmware_list_vms by being network-focused.

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?

The description implies usage (you use it to get network listings) but does not provide explicit guidance on when to use it versus alternatives, nor does it mention any conditions or exclusions. No sibling comparisons are offered.

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