Skip to main content
Glama
vmware-skills

vmware-harden

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_stig_controls

Read-onlyIdempotent

List STIG-aligned vSphere 9 baseline controls, including severity, category, and governed ESXi advanced setting. Read-only pagination reveals exact total, enabling full catalog review before scanning.

Instructions

[READ] List the built-in vSphere 9 / VCF 9 STIG-aligned host baseline's controls (baseline id 'vsphere-stig-v9-subset'). Returns the family list envelope {items, returned, limit, total, truncated, hint}; each item is {id, title, severity (one of critical/high/medium/low/info), category, advanced_setting} where advanced_setting names the ESXi advanced setting the control governs (e.g. 'Security.AccountLockFailures'). total is the exact catalog size, so truncated tells you definitively whether to raise offset. Read-only — parses local baseline YAML only, no database, network, or compliance API (VCF Operations ACC/SPM has none). Use scan_target with baseline 'vsphere-stig-v9-subset' to evaluate these controls against a target; use describe_stig_content_sync for how this catalog is kept in sync.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum rows in this page, must be >= 1 (default 50). The whole catalog is loaded and paged locally, so 'total' stays exact whatever you pass.
offsetNoRows to skip before the page starts, must be >= 0 (default 0 = first page). Raise it by 'limit' while 'truncated' is true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.10.4
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / limit / description
      Added value: +"Maximum rows in this page, must be >= 1 (default 50). The whole catalog is loaded and paged locally, so 'total' stays exact whatever you pass."
    • addedInput schema / properties / offset / description
      Added value: +"Rows to skip before the page starts, must be >= 0 (default 0 = first page). Raise it by 'limit' while 'truncated' is true."
  2. Addedv1.9.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial behavior beyond that: 'parses local baseline YAML only, no database, network, or compliance API' and exact pagination behavior via 'truncated tells you definitively whether to raise offset'. This gives an agent confidence about side effects, latency, and paging in one place.

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 essential purpose, then returns format, then behavioral caveats, then sibling routing. Every sentence carries operational value with no filler, despite the length.

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 specifies the return envelope ({items, returned, limit, total, truncated, hint}) and item fields, including severity enum and advanced_setting example. Combined with parameters and annotations, nothing needed to invoke and interpret the tool 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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuinely useful semantics: the entire catalog is loaded and paged locally, keeping total exact and making truncated a definitive paging signal. This explains why offset/limit behave as they do beyond the schema's field descriptions.

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: 'List the built-in vSphere 9 / VCF 9 STIG-aligned host baseline's controls', including the exact baseline id. This clearly differentiates it from sibling tools like scan_target and list_violations, so an agent knows precisely what the tool returns.

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 routes to alternatives: use scan_target with the same baseline to evaluate controls against a target, and describe_stig_content_sync to learn about catalog sync. It also characterizes the operation as read-only local parsing, making it clear when this listing tool is the right choice.

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