Skip to main content
Glama
AIops-tools

Nutanix AIops

by AIops-tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

cluster_health_rca

Read-only

Analyze Nutanix estate health and utilization to surface worst-first root causes: degraded fault tolerance, storage over 80%/90%, unhealthy nodes, and missing hosts.

Instructions

[READ] Estate health RCA: resiliency state, storage headroom, nodes down.

Collects every cluster's health + utilization, all hosts, and all storage
containers, then reports worst-first findings: degraded fault-tolerance
state, cluster storage pools or containers over 80% (warning) / 90%
(critical), hosts whose nodeStatus is not healthy, and clusters reporting
fewer visible hosts than their nodeCount. Every finding cites the measured
percentage or the raw Prism state string that tripped it.

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

Input Schema

NameRequiredDescriptionDefault
targetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered, but the description adds real behavioral value: it aggregates multiple resource types, reports 'worst-first', applies explicit 80%/90% thresholds, and states that every finding cites the measured percentage or raw Prism state string. Rate limits and auth are not mentioned, keeping it short of a 5.

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?

Front-loaded with the '[READ]' marker and a one-line summary before detail. The enumeration of findings is dense but each clause conveys distinct behavior; slightly long but nothing clearly wasteful.

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?

For a complex multi-source aggregation tool with no output schema, the description details the return findings, thresholds, and evidence format, which is exactly what an agent needs. Coverage is strong, though pagination/ordering beyond 'worst-first' is unstated.

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% for the single 'target' parameter, so the description must compensate — and it does, explaining 'Prism Central target name from config; omit for the default'. That adds meaning beyond the bare anyOf/schema, though it is only one parameter.

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?

States a specific verb and resource ('Estate health RCA'), then enumerates exactly what it collects (every cluster's health + utilization, all hosts, all storage containers) and what it reports. This clearly distinguishes it from single-resource siblings like cluster_health, host_list, and cluster_utilization.

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?

Usage is implied through the scope description (estate-wide RCA) and the '[READ]' tag, but the description never explicitly states when to choose this over cluster_health or cluster_utilization, nor any when-not conditions. It leaves the agent to infer that this is the broad diagnostic versus the narrower siblings.

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