Nutanix MCP Server

Overview Schema Source Related Servers Discussions Admin

pe_get_cluster_info

Retrieve cluster information from a Prism Element node, including AOS version, cluster name, storage capacity, and health status.

Instructions

Get cluster info directly from a Prism Element node. Returns AOS version, cluster name, storage capacity, and health.

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

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.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It only lists return fields but does not disclose whether the operation is read-only, requires authentication, has side effects, or any constraints. The behavioral impact is unclear.

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 a single, compact sentence with no fluff. It front-loads the action and then lists outputs, making it easy to scan.

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?

For a simple tool with one parameter and no output schema, the description provides expected return fields. However, it lacks details on data types or structure of returned values. It is mostly complete given low 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 a clear parameter description ('Prism Element CVM IP address or hostname'). The tool description adds no extra context beyond the schema, so baseline score of 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 the tool gets cluster info from a Prism Element node and enumerates specific return fields (AOS version, cluster name, storage capacity, health). It distinguishes from sibling tools like 'get_cluster' by specifying 'directly from a Prism Element node'.

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?

The description implies usage for direct PE node access but does not explicitly state when to use it vs siblings (e.g., 'get_cluster' for Prism Central). No prerequisites or context for when not to use are provided.

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