Skip to main content
Glama
jkmills

Nutanix MCP Server

by jkmills

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pe_hostYesPrism Element CVM IP address or hostname

Implementation Reference

  • The handler function that executes the pe_list_disks tool. Calls client.pe_list(pe_host, 'disks') and returns disk info including id, uuid, serialNumber, storageTierName, diskStatus, hostName, capacityBytes, and onlineStatus.
    async def handle_pe_list_disks(
        client: NutanixClient, arguments: dict[str, Any]
    ) -> dict[str, Any]:
        """List physical disks from Prism Element v2 API."""
        pe_host = arguments["pe_host"]
        result = await client.pe_list(pe_host, "disks")
        entities = result.get("entities", [])
    
        return {
            "count": len(entities),
            "disks": [
                {
                    "id": d.get("id"),
                    "uuid": d.get("disk_uuid"),
                    "serialNumber": d.get("disk_hardware_config", {}).get("serial_number"),
                    "storageTierName": d.get("storage_tier_name"),
                    "diskStatus": d.get("disk_status"),
                    "hostName": d.get("host_name"),
                    "capacityBytes": d.get("disk_size"),
                    "onlineStatus": d.get("online"),
                }
                for d in entities
            ],
        }
  • The input schema definition for pe_list_disks. Declares the tool name, description, and required parameter 'pe_host' (string) as the Prism Element CVM IP/hostname.
    {
        "name": "pe_list_disks",
        "description": (
            "List physical disks on a Prism Element cluster. "
            "Returns disk type (SSD/HDD), status, capacity, and location."
        ),
        "inputSchema": {
            "type": "object",
            "properties": {
                "pe_host": {
                    "type": "string",
                    "description": "Prism Element CVM IP address or hostname",
                },
            },
            "required": ["pe_host"],
        },
    },
  • Registration of pe_list_disks in the PE_HANDLERS dispatch dictionary, mapping the string 'pe_list_disks' to the handle_pe_list_disks function.
    PE_HANDLERS: dict[str, Any] = {
        "pe_get_cluster_info": handle_pe_get_cluster_info,
        "pe_list_vms": handle_pe_list_vms,
        "pe_list_hosts": handle_pe_list_hosts,
        "pe_list_containers": handle_pe_list_containers,
        "pe_list_storage_pools": handle_pe_list_storage_pools,
        "pe_list_disks": handle_pe_list_disks,
        "pe_list_alerts": handle_pe_list_alerts,
        "pe_list_protection_domains": handle_pe_list_protection_domains,
        "pe_list_snapshots": handle_pe_list_snapshots,
    }
  • MCP server registration: the tool is listed via list_tools() from get_all_tools() and dispatched via call_tool() using the ALL_HANDLERS dict which includes PE_HANDLERS.
    @server.list_tools()
    async def list_tools() -> list[Tool]:
        """Return the list of available tools."""
        return [
            Tool(
                name=tool["name"],
                description=tool["description"],
                inputSchema=tool["inputSchema"],
            )
            for tool in all_tools
        ]
  • Helper method pe_list() in NutanixClient that sends a GET request to the Prism Element v2 API for listing resources (e.g., 'disks'). This is what the handler calls.
    async def pe_list(
        self,
        pe_host: str,
        resource: str,
        count: Optional[int] = None,
        filter_criteria: Optional[str] = None,
    ) -> dict[str, Any]:
        """List resources from a Prism Element node using v2 API.
    
        Args:
            pe_host: Prism Element CVM IP or hostname
            resource: Resource type (e.g., 'vms', 'hosts', 'disks', 'containers')
            count: Max results to return
            filter_criteria: Filter string for the query
        """
        params: dict[str, str] = {}
        if count is not None:
            params["count"] = str(count)
        if filter_criteria:
            params["filter_criteria"] = filter_criteria
    
        return await self.pe_get(pe_host, resource, params=params)
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.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jkmills/nutanix-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server