Skip to main content
Glama
vmware-skills

VMware-Monitor

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_cluster_health_summary

Read-onlyIdempotent

Summarize health of every vSphere cluster in one call: roll up hosts, VM power, CPU/memory pressure, and alarms into ok/warn/critical scores with top issues.

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. top_issues includes datastores thin-provisioned past 100% of capacity (kind capacity, scope datastore), attributed to the cluster of a host that mounts them; get_datastore_capacity has the full table. Alarm issues carry condition_now and acknowledged_days. Only a cleared alarm (its condition is read to be false now) ranks after live issues; an unknown one is not re-checked and keeps its severity rank, however long ago it was acknowledged — report it as possibly still live.

Then drill into what top_issues names with investigate_vm, investigate_host or investigate_datastore; use get_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. Addedv2.2.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare read-only/idempotent, but the description adds substantial behavior beyond them: it is point-in-time with no trending, top_issues is ranked worst-first, cleared vs unknown alarm handling differs, and thin-provisioned datastores past 100% are folded in. These are exactly the nuances an agent needs and none are derivable from the annotations.

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-loads the core purpose and is organized into scannable blocks (purpose, return shape, alarm nuance, drill-down). It is on the long side and the alarm-paragraph is dense, but nearly every sentence carries actionable meaning, so waste is limited.

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?

With no output schema, the description compensates by enumerating the return keys ({totals, top_issues, issues_total, clusters, snapshot, customization_hint}), explaining what each leads with, and clarifying that it is not the list envelope. Nothing needed to call and interpret it 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 coverage is 100% and each parameter is well documented there, so the baseline is 3. The description reinforces a couple of semantics (top_issues capping, cluster_filter behavior) but adds little beyond what the schema descriptions already state.

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+resource ('health rollup for every cluster') and immediately frames the intent with a memorable question ('is anything on fire?'). It explicitly distinguishes itself from siblings by naming list_all_clusters + list_esxi_hosts + get_alarms as the thing it replaces.

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?

Explicitly says when to use it ('Start here for single-vCenter triage'), when not to stitch the primitives yourself, and routes follow-up work to investigate_vm/investigate_host/investigate_datastore and get_cross_vcenter_attention. It even delegates remediation ('Acting on a finding belongs to vmware-aiops').

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