Skip to main content
Glama
Sign In
vmware-knight

vmware-knight

by CyberKnightLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_dvs_portgroups

Read-onlyIdempotent

List distributed virtual portgroups with binding type, VLAN, port count, and uplink status. Scope by dvSwitch to verify portgroup creation or survey network configuration before changes.

Instructions

[READ] List distributed virtual portgroups, optionally scoped to one dvSwitch.

Per portgroup: name, parent dvSwitch, binding type (earlyBinding / ephemeral), VLAN setting (id, trunk ranges, or pvlan), configured port count, and whether it is the switch's uplink portgroup. Use to verify create_dvs_portgroup results or to survey network config before changes.

Returns: The family list envelope {items, returned, limit, total, truncated, hint}; each item is one portgroup. portgroups is kept as a deprecated alias for items. Errors return a dict with "error" + hint.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax portgroups to return (default 200).
offsetNoSkip this many portgroups first (paging).
targetNovCenter target name from config.yaml; omit to use the default target.
dvs_nameNodvSwitch name to scope to; omit to list across all switches.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.12.10

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive, and the description adds substantial behavioral context: the exact fields returned per portgroup, the family list envelope, the deprecated alias for items, and the error dict shape. This goes well beyond what annotations alone provide.

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 front-loaded with the action, followed by useful use-case and output details. Every sentence adds value: scoping, per-item fields, when to use it, and the response shape and error format. It is informative without being bloated.

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?

Despite the absence of an output schema, the description fully explains the return envelope, item contents, deprecated alias, and error behavior. Combined with the well-documented input schema and safety annotations, an agent has enough to select and invoke the tool correctly.

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%, so the schema already documents all four parameters and their defaults. The description only reinforces that dvs_name scopes the listing, which adds context but does not materially expand on the schema.

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 names a specific verb and resource ('List distributed virtual portgroups') and adds the optional dvSwitch scoping. It distinguishes itself from siblings like create_dvs_portgroup by clearly being the read-side counterpart, and no sibling covers the same resource and action.

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?

The description explicitly says when to use it: 'verify create_dvs_portgroup results or to survey network config before changes.' It does not spell out when not to use it or name alternative tools, so it stops one step short of the top score.

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

Deploy Server

Other Tools