Nutanix MCP Server

by jkmills

Overview Schema Source Related Servers Discussions Admin

Python

Remote

pe_list_hosts

Lists hypervisor hosts on a Prism Element cluster, returning names, IPs, hardware specifications, and CVM information.

Instructions

List hypervisor hosts on a Prism Element cluster. Returns host names, IPs, hardware specs, and CVM info.

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_hosts"
  }
}

Input Schema

Name	Required	Description	Default
`pe_host`	Yes	Prism Element CVM IP address or hostname

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 7, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations provided, so description carries burden. It states the tool lists hosts and returns specific fields, implying a read-only operation. However, it does not disclose any behavioral traits like permissions required, rate limits, or potential complexity of the returned data.

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 sentences, front-loaded with purpose, no wasted words. Efficiently conveys the tool's action and output scope.

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 tool's simplicity (one parameter, list operation), the description adequately covers purpose and output fields. Could mention potential limits like pagination or data size, but overall complete for its complexity.

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 one parameter 'pe_host' described as 'Prism Element CVM IP address or hostname'. Description does not add additional semantic meaning beyond the schema, so baseline 3 applies.

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 verb 'List' and resource 'hypervisor hosts on a Prism Element cluster'. It specifies return fields (host names, IPs, hardware specs, CVM info), distinguishing it from sibling tool 'list_hosts' which likely targets Prism Central.

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 like 'list_hosts'. Context implies it is for Prism Element only, but does not state when not to use it or mention any prerequisites.

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