Skip to main content
Glama

list_violations

Retrieve compliance violations from the most recent scan snapshot, with optional severity filtering and pagination.

Instructions

[READ] List compliance violations recorded by the most recent scan snapshot in the local twin DB (~/.vmware-harden/twin.duckdb). severity (optional string): filter to exactly one of 'critical', 'high', 'medium', 'low', 'info'; omit to return all severities. limit (optional int, default 50): max rows returned; offset (optional int, default 0): rows to skip for paging. Returns an envelope {violations: [...], total, limit, offset, has_more}; each violation is {id, rule_id, node_id, severity, baseline_id, evidence}, sorted severity-descending then rule_id. total is the full matching count (unbounded by limit) so nothing is hidden — page by raising offset while has_more is true. Empty envelope (total 0) when no scan exists — run scan_target first. Read-only local DB query, no network calls. Pass a row's 'id' to get_remediation for a fix plan.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo
severityNo
Behavior5/5

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

With no annotations, the description carries full burden. It discloses read-only local DB access, no network calls, sorting order, envelope structure with total/has_more, and empty-behavior when no scan exists. This is comprehensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured and front-loaded with purpose. Every sentence adds value, though slightly lengthy. Could be tightened without losing clarity, but overall efficient.

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?

Given no output schema, the description fully documents the return envelope, paging, sorting, and error case (no scan). Also mentions related tool (get_remediation). Complete for typical usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but description fully explains each parameter: severity options explicitly listed, limit/offset defaults and paging semantics. Adds meaning beyond schema types.

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 clearly states the verb+resource: 'List compliance violations recorded by the most recent scan snapshot in the local twin DB'. This distinguishes it from siblings like scan_target (runs scan) and get_remediation (fix plan).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear usage context: explains when to use (to list violations), when not (empty envelope means run scan_target first), and how to page. Links to get_remediation. Does not explicitly contrast with list_drift_events or list_baselines, but the purpose is self-evident.

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/zw008/VMware-Harden'

If you have feedback or need assistance with the MCP directory API, please join our Discord server