Nutanix MCP Server

by jkmills

Overview Schema Source Related Servers Discussions Admin

Python

Remote

get_cluster

Retrieve detailed configuration, network, storage, and health information for a Nutanix cluster using its UUID.

Instructions

Get detailed information about a specific cluster by UUID. Returns configuration, network, storage, and health details.

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": {
      "cluster_uuid": "<cluster_uuid>"
    },
    "name": "get_cluster"
  }
}

Input Schema

Name	Required	Description	Default
`cluster_uuid`	Yes	The UUID (extId) of the cluster

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 7, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description must fully convey behavioral traits. It describes what is returned but does not disclose that this is a read-only operation, any authentication requirements, rate limits, or potential side effects. The lack of such information reduces transparency.

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 sentence that efficiently conveys the purpose and key details. No unnecessary words, and the core action is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple get tool with one parameter and no output schema, the description covers the essential purpose and return categories. However, it lacks information about potential error cases, response format, or pagination (if applicable). It is adequate but not comprehensive.

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 description coverage is 100% for the single parameter, so the baseline is 3. The description adds the context 'by UUID' but the schema already describes the parameter as 'The UUID (extId) of the cluster'. No additional semantic value is provided beyond the schema.

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 action ('Get detailed information'), the resource ('cluster'), and the scope ('by UUID'). It also lists the categories of details returned (configuration, network, storage, health). This distinguishes it from sibling tools like list_clusters (which returns summaries) and other get_* tools.

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 when you have a specific cluster UUID and need detailed info, but it does not explicitly state when to use this tool vs alternatives (e.g., list_clusters for listing all clusters, or pe_get_cluster_info for Prism Element). No exclusions or prerequisites are mentioned.

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