Skip to main content
Glama

alert_triage_rca

Triage unresolved Nutanix Prism alerts: get severity counts, spot critical alerts without acknowledgment, and view the oldest unresolved alert to prioritize root cause investigation.

Instructions

[READ] Triage active Prism alerts: per-severity counts + oldest unresolved.

Groups every unresolved alert by severity with a count per level, flags
critical alerts nobody has acknowledged, and surfaces the oldest unresolved
alert with its age in days (aged against the newest alert in the same feed,
so the analysis is clock-free and reproducible). Use analyze_alert on an
individual extId for the per-alert event correlation.

Args:
    target: Prism Central target name from config; omit for the default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNo
Behavior4/5

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

No annotations provided, but description mentions 'READ' and explains aggregation logic (clock-free, reproducible). Enough for a read-only tool with no destructive hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise overall, but the age computation sentence is somewhat lengthy. Well-structured with initial summary and detailed explanation.

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?

Lacks details on output structure (e.g., format of counts, oldest alert fields). Given no output schema, more info would help.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but description explains 'target' parameter as Prism Central target name; omit for default. Adds meaning beyond 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?

Description clearly states it triages active Prism alerts with per-severity counts and oldest unresolved alert. Distinct from siblings like analyze_alert, alert_list, etc.

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

Usage Guidelines4/5

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

Explicitly recommends using analyze_alert for per-alert correlation, but lacks negative guidance or comparison to other siblings like alert_list.

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/AIops-tools/Nutanix-AIops'

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