Skip to main content
Glama
vmware-skills

VMware-Monitor

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ntp_status

Read-onlyIdempotent

Check NTP configuration health across vCenter hosts: verifies servers configured and ntpd running, flags unreachable hosts, and compares server consistency to identify clock drift risks.

Instructions

[READ] Per-host NTP configuration health (servers + ntpd service state).

Returns the list envelope; every matching host is enumerated, so truncated is always False. Each row has host, reachable, ntp_servers, ntpd_running, ntpd_policy and a healthy flag (servers configured AND ntpd running). The SOAP API does not expose live clock offset or stratum — this is configuration health only; for actual offset use esxcli on the host.

healthy/ntp_servers/ntpd_running are null — not false/empty — for a host vCenter could not reach or could not read. Null means nothing was observed; false means NTP is misconfigured. Filtering rows for healthy == false will not surface the unread ones, so check the envelope's hosts_unreachable count and unreachable_note before reporting the estate as healthy.

The envelope's ntp_sources_consistent compares hosts with each other: false when hosts that have servers configured use different ones (each row can still be healthy — this is how clocks drift apart), with ntp_sources_note naming which host uses which servers; null when fewer than two hosts have servers to compare.

Prefer this over get_host_services for time problems: that tool reports whether ntpd runs but not which servers are configured. Fixing NTP is a write; use vmware-aiops.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.

  1. Changed4 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 / 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": "ntp_statusOutput",
-  "type": "object"
-}New value: +null
  2. Addedv1.6.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, and the description adds significant behavioral detail beyond that: truncated is always False, null vs false semantics, unreachable hosts appear in the envelope, ntp_sources_consistent compares hosts, and the SOAP API limitation is disclosed. No contradiction with annotations.

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 long but every sentence adds necessary nuance: return envelope behavior, null semantics, comparison logic, limitations, and alternative tool guidance. It is front-loaded with the core purpose and progresses logically from row-level details to envelope-level and then to usage guidance. No filler or redundancy.

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 fully compensates by enumerating row fields (host, reachable, ntp_servers, ntpd_running, ntpd_policy, healthy), envelope fields (truncated, hosts_unreachable, unreachable_note, ntp_sources_consistent, ntp_sources_note), and explaining edge cases. It also covers API limitations and alternative approaches, making it complete for correct invocation and interpretation.

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 target and host_name documented clearly in the input schema. The description adds context about matching hosts and envelope behavior but does not need to repeat parameter meanings. Baseline 3 is appropriate because the schema carries the semantic load.

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 specific verb and resource: '[READ] Per-host NTP configuration health (servers + ntpd service state)'. It precisely defines what is measured (configuration health, not live clock offset) and explicitly differentiates itself from the sibling get_host_services by noting that tool lacks server configuration details.

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?

The description explicitly says to prefer this tool over get_host_services for time problems and gives the reason why. It also states that fixing NTP is a write operation and should use vmware-aiops, clearly distinguishing read vs. write use cases and routing the agent to the correct alternative.

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