Skip to main content
Glama
vmware-skills

VMware-Monitor

by vmware-skills
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

get_host_sensors

Read-onlyIdempotent

Retrieve physical host sensor status (temperature, voltage, fan) with green/yellow/red health markers to spot failing hardware across vCenter hosts.

Instructions

[READ] Get hardware sensor status (temperature, voltage, fan, ...) for all hosts.

Returns the list envelope with a real total; each row has host, sensor_name, type, reading, unit and status (green/yellow/red). Empty items means no host exposes sensor data (e.g. nested ESXi), not that the query failed.

Use this for physical hardware only — for CPU/memory load use host_performance, and follow up on a red sensor with host_investigation_bundle to see the alarms and events around that host.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax sensor rows to return (None = all).
targetNovCenter/ESXi target from config (default if omitted).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.9.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / limit / description
      Added value: +"Max sensor rows to return (None = all)."
    • 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_host_sensorsOutput",
-  "type": "object"
-}New value: +null
  2. Addedv1.5.38

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive. The description adds valuable behavioral detail beyond those structured hints: it documents the list envelope's real 'total', the row fields, the green/yellow/red status values, and the critical meaning of empty 'items' as 'no host exposes sensor data' rather than a failed query. This directly prevents a common false-negative interpretation.

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?

Three short paragraphs each serve a distinct purpose: what it returns, how to interpret empty results, and when to use alternatives. The most important facts are front-loaded, and there is no filler or repetition. Every sentence earns its place.

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 listing tool with no output schema, this description is complete: it covers purpose, returned fields, status semantics, empty-result interpretation, and routing to related tools. An agent has everything it needs to invoke the tool correctly and interpret the result without further inference.

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% with both 'limit' and 'target' already documented: 'Max sensor rows to return (None = all)' and 'vCenter/ESXi target from config (default if omitted)'. The description does not add parameter-level syntax or examples, so the baseline 3 is appropriate because the schema carries the parameter meaning.

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: 'Get hardware sensor status (temperature, voltage, fan, ...) for all hosts.' It clearly names the resource, scope, and data categories, and distinguishes itself from siblings through the 'physical hardware only' framing. This is far beyond a tautology and gives an agent an immediate mental model of the tool.

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 tells when to use this tool ('physical hardware only'), names the alternative for load data ('host_performance'), and gives a follow-up action for red sensors ('host_investigation_bundle'). It also explains an edge case (nested ESXi) to prevent misinterpretation. This is model guidance for when-to-use vs alternatives.

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