Skip to main content
Glama
vmware-skills

VMware-Monitor

by vmware-skills
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

get_events

Read-onlyIdempotent

Fetch recent vCenter/ESXi events filtered by severity for an inventory-wide sweep, helping identify critical warnings and unknown classifications across hosts.

Instructions

[READ] Get recent vCenter/ESXi events filtered by severity.

Returns the list envelope. No row limit is applied, so truncated is False; total is null because vCenter's event collector applies its own bounds — widen hours if you need to be sure nothing older is being missed.

Severity is this skill's own ranking where it has one, and otherwise vCenter's published event catalogue. An event neither can rank comes back with severity "unknown" (it is returned, not filtered out) and is counted in the envelope's unclassified, with classification_note explaining. An empty items alongside a non-zero unclassified does NOT mean the window was quiet — read the note before reporting all-clear.

Use this for an inventory-wide event sweep. When you already know the object, prefer vm_investigation_bundle / host_investigation_bundle instead: they return the same events correlated with that object's state in one call. ESXi syslog lines are not events — use host_log_scan for those.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hoursNoHow many hours back to query (default 24).
targetNovCenter/ESXi target from config (default if omitted).
severityNoMinimum severity: "critical", "warning", or "info".warning

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed6 schema fields changedv1.9.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / hours / description
      Added value: +"How many hours back to query (default 24)."
    • addedInput schema / properties / severity / description
      Added value: +"Minimum severity: \"critical\", \"warning\", or \"info\"."
    • addedInput schema / properties / severity / enum
      Added value: +[
+  "critical",
+  "warning",
+  "info"
+]
    • addedInput schema / properties / target / description
      Added value: +"vCenter/ESXi target from config (default if omitted)."
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "items": {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      "title": "Result",
-      "type": "array"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_eventsOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.2

TDQS

A4.9/5.0
Behavior5/5

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

The annotations already mark the tool read-only and idempotent, but the description adds substantial behavioral context beyond them: the envelope behavior, the reason total is null, the 'unknown' severity being returned rather than filtered, the unclassified counter, and the warning that empty items plus non-zero unclassified does not mean a quiet window. This is exactly the kind of nuance an agent needs to interpret results correctly.

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 longer than typical, but every sentence carries essential interpretive or routing information. It is front-loaded with the core purpose, then builds through envelope semantics, severity quirks, and finally sibling-tool differentiation. No filler or redundancy is present; the length is justified by the subtle failure modes it prevents.

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 tool with no output schema, the description thoroughly explains the return envelope, key fields, caveats, and the unclassified/unknown edge cases. It also covers when to use this tool versus correlated bundles and log scanning. Given the tool's complexity, nothing needed for correct invocation or result interpretation is missing.

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?

The input schema already covers all three parameters with 100% description coverage, so the baseline is 3. The description adds meaningful extra semantics for hours ('widen hours if you need to be sure nothing older is being missed') and severity (ranking behavior and 'unknown' handling), elevating it above baseline. Target is not elaborated, but the schema already describes it sufficiently.

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 opens with a clear '[READ] Get recent vCenter/ESXi events filtered by severity', identifying the exact verb, resource, and filtering dimension. It further differentiates from siblings by framing this as an 'inventory-wide event sweep' and explicitly contrasting with vm_investigation_bundle / host_investigation_bundle, making selection unambiguous.

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?

Usage guidance is explicit: 'Use this for an inventory-wide event sweep' states when to call it, and it names the preferred alternatives when the object is already known. It also excludes a common confusion case by stating ESXi syslog lines are not events and routing to host_log_scan. No inference is required.

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/vmware-skills/VMware-Monitor'

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