Skip to main content
Glama
jkmills

Nutanix MCP Server

by jkmills

pe_list_alerts

List active or resolved alerts from a Prism Element cluster, including severity, timestamps, and affected entities.

Instructions

List alerts on a Prism Element cluster. Returns alert titles, severity, timestamps, and affected entities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pe_hostYesPrism Element CVM IP address or hostname
resolvedNoInclude resolved alerts (default: false, only active)
countNoMaximum number of alerts to return (default: 50)

Implementation Reference

  • Schema registration for 'pe_list_alerts' tool: defines the tool name, description, and input schema (requires pe_host, optional resolved boolean defaulting to False, optional count integer defaulting to 50).
    {
        "name": "pe_list_alerts",
        "description": (
            "List alerts on a Prism Element cluster. "
            "Returns alert titles, severity, timestamps, and affected entities."
        ),
        "inputSchema": {
            "type": "object",
            "properties": {
                "pe_host": {
                    "type": "string",
                    "description": "Prism Element CVM IP address or hostname",
                },
                "resolved": {
                    "type": "boolean",
                    "description": "Include resolved alerts (default: false, only active)",
                    "default": False,
                },
                "count": {
                    "type": "integer",
                    "description": "Maximum number of alerts to return (default: 50)",
                    "default": 50,
                },
            },
            "required": ["pe_host"],
        },
    },
  • Handler function for 'pe_list_alerts' tool: calls client.pe_get(pe_host, 'alerts', params=params) with optional resolved=false filter, then returns alert titles, severity, timestamps, and affected entities.
    async def handle_pe_list_alerts(
        client: NutanixClient, arguments: dict[str, Any]
    ) -> dict[str, Any]:
        """List alerts from Prism Element v2 API."""
        pe_host = arguments["pe_host"]
        resolved = arguments.get("resolved", False)
        count = arguments.get("count", 50)
    
        params: dict[str, str] = {"count": str(count)}
        if not resolved:
            params["resolved"] = "false"
    
        result = await client.pe_get(pe_host, "alerts", params=params)
        entities = result.get("entities", [])
    
        return {
            "count": len(entities),
            "alerts": [
                {
                    "id": a.get("id"),
                    "alertTitle": a.get("alert_title"),
                    "severity": a.get("severity"),
                    "message": a.get("message"),
                    "resolved": a.get("resolved"),
                    "createdTimeStamp": a.get("created_time_stamp_in_usecs"),
                    "affectedEntities": a.get("affected_entities", []),
                }
                for a in entities
            ],
        }
  • Handler dispatch dict PE_HANDLERS mapping the string 'pe_list_alerts' to the handle_pe_list_alerts 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,
    }
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It fails to disclose behavioral traits such as read-only nature, authentication needs, or side effects. It only states what is returned.

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 succinct sentences, front-loaded with the main purpose, no redundant or filler content.

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 3 parameters and no output schema. It lists return fields but could mention default behavior of 'resolved' or pagination via 'count'.

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%, so baseline is 3. The description adds minimal context (Prism Element cluster) but doesn't provide additional meaning beyond the schema's parameter descriptions.

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 (list), the resource (alerts on a Prism Element cluster), and the return value (titles, severity, timestamps, affected entities). It distinguishes from sibling tools like pe_list_vms or list_hosts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives, no prerequisites or context for selection. For example, it doesn't clarify when to prefer pe_list_alerts over generate_environment_report.

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