Nutanix MCP Server

Overview Schema Source Related Servers Discussions Admin

pe_list_storage_pools

List storage pools on a Prism Element cluster to retrieve pool names, capacity, and disk composition for capacity planning and inventory management.

Instructions

List storage pools on a Prism Element cluster. Returns pool names, capacity, and disk composition.

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

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?

No annotations; description adds context beyond schema by listing return data. Does not disclose pagination or error behaviors, but for a simple list tool this is acceptable.

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, no wasted words. Front-loaded with purpose and return information.

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?

Adequate for a simple list tool with one parameter. Missing potential error context, but sufficiently covers purpose and output.

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% (one param with description). Description does not add additional meaning to the parameter 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?

Clear verb 'list', specific resource 'storage pools', and states returned fields (names, capacity, disk composition). Distinguished from sibling 'list_storage_containers'.

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 when-to-use or alternatives. Implied usage from name and description, but lacks guidance compared to other list tools.

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