Nutanix MCP Server

Overview Schema Source Related Servers Discussions Admin

pe_list_vms

List virtual machines on a Prism Element cluster, retrieving names, UUIDs, power states, and resource allocation for specified hosts.

Instructions

List VMs on a specific Prism Element cluster. Returns VM names, UUIDs, power states, and resource allocation.

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": {
      "pe_host": "<pe_host>"
    },
    "name": "pe_list_vms"
  }
}

Input Schema

Name	Required	Description	Default
`pe_host`	Yes	Prism Element CVM IP address or hostname
`count`	No	Maximum number of VMs to return

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations provided, so description carries full burden. It explicitly states return values (names, UUIDs, power states, resource allocation) and implies read-only operation. Could add authentication details but sufficient for typical list tool.

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 concise sentences, each providing essential information: purpose and return fields. No unnecessary 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 simple nature of the tool with 2 parameters and no output schema, the description covers purpose, scope, and return fields. Could mention pagination or error handling but overall adequate.

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% with descriptions for pe_host and count. Description does not add additional meaning beyond what 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?

Clearly states verb 'List', resource 'VMs', and scope 'on a specific Prism Element cluster', distinguishing from general list_vms sibling. Also specifies returned fields.

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?

Description implies usage for specific Prism Element clusters, which differentiates from related tools. No explicit when-not or alternatives, but context is clear.

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