Skip to main content
Glama

Get compliance reports

get_compliance_reports
Read-only

Get the Trivy Operator compliance posture for the current cluster. Returns bounded benchmark identities and pass/fail totals, failed controls with severity, remediation and affected counts, passed controls, and the aggregated configuration-audit severity, namespace and top-check rollups. For one selected finding, pass a focus object with check_id and source, plus benchmark_id for a benchmark control. Focused responses contain only that exact control and report whether it matched. Do not broaden a focused remediation request to unrelated controls. Use this for CIS, NSA/CISA and other compliance-benchmark questions; use get_security_reports for image vulnerabilities and CVEs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cluster_id": "<cluster_id>"
    },
    "name": "get_compliance_reports"
  }
}

Input Schema

NameRequiredDescriptionDefault
focusNoExact selected control. Omit for a general cluster posture read.
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, so the description carries the rest and does so: it enumerates the returned data (benchmark identities, pass/fail totals, failed controls with severity/remediation/affected counts, rollups) and discloses the key behavioral quirk of focus mode — the response contains only the exact control and reports whether it matched.

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?

Front-loaded with purpose, then return contents, then focus usage, then sibling routing — a sensible order. It is dense and slightly list-heavy, but nearly every clause carries information an agent needs.

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 and a nested focus object, the description compensates by describing the response structure and the focused-response behavior, and it names the sibling to use for vulnerability questions. Nothing material is missing for correct invocation.

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 baseline is 3; the description adds the semantic rule that a focus object is optional and that omitting it yields a general cluster posture read, plus that benchmark_id is needed for benchmark-sourced controls. Those points largely restate schema descriptions, which caps it short of 5.

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?

Opens with a specific verb+resource: 'Get the Trivy Operator compliance posture for the current cluster', and immediately distinguishes itself from get_security_reports (image vulnerabilities/CVEs). An agent can tell what it returns and what it does not.

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 names the domain of use (CIS, NSA/CISA and other compliance-benchmark questions) and the alternative for a different domain (get_security_reports for image vulns). It also states the focused-vs-general mode choice and warns not to broaden a focused remediation request to unrelated controls.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.