Nutanix MCP Server

by jkmills

Overview Schema Source Related Servers Discussions Admin

Python

Remote

pe_list_disks

List physical disks on a Nutanix Prism Element cluster, retrieving disk type, status, capacity, and location.

Instructions

List physical disks on a Prism Element cluster. Returns disk type (SSD/HDD), status, capacity, and location.

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

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

A4/5.0

Behavior4/5

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

The description discloses the return fields (disk type, status, capacity, location) beyond just 'list', which is helpful. With no annotations, it provides behavioral insight. However, it does not mention whether the operation is read-only or any potential side effects.

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 the action, then enumerating return fields. No redundant words, highly efficient.

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?

The description covers the purpose and key return fields. Although there is no output schema, the listed fields (type, status, capacity, location) provide a good overview. Could mention additional details like disk IDs or usage, but it's 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?

The single parameter 'pe_host' is fully described in the schema (100% coverage). The tool description adds no additional semantics beyond 'on a Prism Element cluster', which matches the schema. 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 it lists physical disks on a Prism Element cluster, specifying the resource (disks) and scope (cluster). Among sibling tools like pe_list_hosts and pe_list_containers, this distinguishes itself by targeting disks.

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 or when not to use this tool, nor mentions of prerequisites or alternatives. The context signals (sibling tools) imply it is for disk listing, but explicit usage guidelines are missing.

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