Skip to main content
Glama
vmware-skills

VMware-Monitor

by vmware-skills
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

host_log_scan

Read-onlyIdempotent

Scan recent ESXi host syslog lines to detect error and warning patterns, revealing root causes of host issues when vCenter events are inconclusive.

Instructions

[READ] Scan recent ESXi host syslog lines for error/warning patterns.

Reads the last lines entries of the hostd/vmkernel/vpxa logs via the diagnostic system and returns only the lines matching known trouble patterns (error, fail, critical, panic, lost access, timeout, …). Returns the list envelope {items, returned, limit, total, truncated, hint}; each row has severity, source (host_log:<key>), message, time and entity. total is null on purpose — this is "errors within the scanned window", not all errors ever, and empty items means nothing matched.

Use this when get_events or host_investigation_bundle show a host in trouble but not why: vCenter events and ESXi syslog are different sources. Filter with host_name to keep the scan fast on large clusters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linesNoHow many recent lines per log to scan (default 500).
targetNovCenter/ESXi target from config (default if omitted).
host_nameNoFilter to a single host by exact name (None = all hosts).

Schema Changelog

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

  1. Changed5 schema fields changedv1.9.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / host_name / description
      Added value: +"Filter to a single host by exact name (None = all hosts)."
    • addedInput schema / properties / lines / description
      Added value: +"How many recent lines per log to scan (default 500)."
    • 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": "host_log_scanOutput",
-  "type": "object"
-}New value: +null
  2. Addedv1.6.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already establish readOnly, idempotent, and non-destructive behavior, and the description adds valuable behavioral detail: it explains that only matching lines are returned, describes the envelope format, and notably clarifies that 'total is null on purpose' and empty items means no matches. This prevents misinterpretation of scan results.

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 earns its place. It front-loads the core purpose, then covers behavior, return format, the total-null caveat, and usage guidance without repetition or filler.

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?

The tool has no output schema, but the description fully covers the return envelope and row fields, plus the semantics of total and empty items. Combined with the complete input schema and annotations, nothing essential is missing for correct invocation and interpretation.

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 100%, so the baseline is 3, but the description adds useful parameter context beyond the schema: it explains that 'lines' is per log and that 'host_name' can narrow the scan for performance. It does not add much for 'target', but the schema already adequately documents that 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?

The description states a specific action ('Scan recent ESXi host syslog lines for error/warning patterns') against a clear resource. It also differentiates from related tools by noting that vCenter events and ESXi syslog are different sources, which helps an agent select this tool among siblings like get_events and host_investigation_bundle.

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 the tool: 'Use this when get_events or host_investigation_bundle show a host in trouble but not why.' It also provides an optimization hint: 'Filter with host_name to keep the scan fast on large clusters.' This goes well beyond a vague context statement.

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