Skip to main content
Glama
Sign In
Nutanix MCP Server

Nutanix MCP Server

by jkmills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

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.

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

Input 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)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 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.

Deploy Server

Other Tools