Skip to main content
Glama
vmware-skills

VMware-Monitor

by vmware-skills
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

license_status

Read-onlyIdempotent

Check vCenter/ESXi license usage and expiration to identify over-allocation and approaching renewals. Returns the complete license inventory with total/used units and expiry per license.

Instructions

[READ] vCenter/ESXi license inventory with usage and expiry.

Returns the list envelope, one row per license: name, edition_key, total/used units, unlimited flag (row total == 0) and expiration. Every license is enumerated, so truncated is always False — this is the complete inventory.

Use this to catch over-allocation or an approaching expiry, alongside certificate_status and ntp_status for a platform-hygiene sweep. Which host consumes which license is not reported — use list_esxi_hosts for the host inventory. Assigning a license is a write; use vmware-aiops.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNovCenter/ESXi target from config (default if omitted).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.9.2
    • addedInput schema / additionalProperties
      Added value: +false
    • 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": "license_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 this as read-only, idempotent, and non-destructive. The description adds meaningful behavioral detail beyond that: it documents the list envelope, per-row fields, the unlimited flag semantics ('row total == 0'), and guarantees 'truncated is always False' because every license is enumerated. It also discloses what is not reported.

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 front-loaded with the core purpose and [READ] marker, then returns semantics, usage context, exclusions, and alternatives. Each sentence contributes distinct information with no redundant fluff.

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 carries the burden of explaining return contents, which it does thoroughly: envelope type, row fields, unlimited flag semantics, and truncation behavior. It also covers scope limitations and related tools, making the tool self-sufficient for correct invocation.

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?

The sole parameter 'target' has 100% schema description coverage: 'vCenter/ESXi target from config (default if omitted).' The description adds no additional parameter-specific meaning, which is acceptable because the schema already carries the necessary semantics.

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 names a specific verb and resource: '[READ] vCenter/ESXi license inventory with usage and expiry.' It also distinguishes itself from siblings by explicitly stating that host-level license consumption is not reported and pointing to list_esxi_hosts, and by noting that license assignment belongs to vmware-aiops.

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 context is explicit: 'Use this to catch over-allocation or an approaching expiry' and it is framed as part of a platform-hygiene sweep with certificate_status and ntp_status. It also gives clear when-not-to-use guidance: host consumption is handled by list_esxi_hosts and license assignment by vmware-aiops.

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