Skip to main content
Glama
vmware-skills

VMware-Monitor

by vmware-skills
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

cluster_health_summary

Read-onlyIdempotent

Assess cluster health by rolling up hosts, VM state, CPU/memory pressure, and alarms per cluster, then rank anomalies into top issues for immediate triage.

Instructions

[READ] One-glance health rollup for every cluster — "is anything on fire?".

Start here for single-vCenter triage. Batches hosts, VM power state, live CPU/memory pressure and alarms per cluster, scores each "ok"/"warn"/ "critical", and ranks the anomalies into top_issues. Use this instead of stitching list_all_clusters + list_esxi_hosts + get_alarms yourself.

Returns {totals, top_issues, issues_total, clusters, snapshot, customization_hint} — not the list envelope. Lead with top_issues (worst first), show clusters as context, always echo customization_hint last. Point-in-time — no trending.

Then drill into what top_issues names with vm_investigation_bundle, host_investigation_bundle or datastore_investigation_bundle; use cross_vcenter_attention to cover every target at once. Acting on a finding belongs to vmware-aiops.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
top_nNoCap ``top_issues`` (default 10; 0 omits it). ``issues_total`` is the pre-cap count.
targetNovCenter/ESXi target from config (default if omitted).
include_vmsNoRoll up VM counts (default True); False skips that pass.
cluster_filterNoCase-insensitive substring; only matching clusters show (None = all, plus a standalone-hosts row).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.9.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / cluster_filter / description
      Added value: +"Case-insensitive substring; only matching clusters show (None = all, plus a standalone-hosts row)."
    • addedInput schema / properties / include_vms / description
      Added value: +"Roll up VM counts (default True); False skips that pass."
    • addedInput schema / properties / target / description
      Added value: +"vCenter/ESXi target from config (default if omitted)."
    • addedInput schema / properties / top_n / description
      Added value: +"Cap ``top_issues`` (default 10; 0 omits it). ``issues_total`` is the pre-cap count."
  2. Addedv1.7.6

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, and the description reinforces this with '[READ]'. It adds valuable behavior beyond annotations: the return envelope shape, the 'not the list envelope' caveat, the point-in-time/no-trending limitation, and the instruction to echo customization_hint last.

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?

The description is dense but every sentence carries distinct value: purpose, use case, alternative, return behavior, point-in-time semantics, and drill-down routing. It is front-loaded with the core purpose and remains highly scannable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only aggregation tool with no output schema, the description supplies the necessary return keys, the ranking behavior, the absence of trending, and the recommended next steps. All parameters are already fully described in the schema, so nothing needed to invoke the tool correctly is missing.

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 the schema fully documents all four parameters. The description does not add parameter-specific detail beyond what the schema already provides, which makes the baseline 3 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 identifies the tool as a one-glance health rollup for clusters, with a specific verb ('rollup', 'scores', 'ranks') and resource ('every cluster'). It distinguishes itself from sibling tools by explicitly saying to use it instead of stitching list_all_clusters + list_esxi_hosts + get_alarms.

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

Usage Guidelines5/5

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

It explicitly says 'Start here for single-vCenter triage' and names the exact alternative tools for drill-down (vm_investigation_bundle, host_investigation_bundle, datastore_investigation_bundle) and broader coverage (cross_vcenter_attention). It even tells the agent that acting on a finding belongs to vmware-aiops, which is strong routing guidance.

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