Skip to main content
Glama

Get security reports

get_security_reports
Read-only

Get the Trivy Operator image-vulnerability summary for the current cluster. Returns: total findings broken down by severity (critical/high/medium/low), severity split by scope (workload images vs cluster-wide), the top ecosystems, a prioritised queue of the most important CVEs ranked by blast radius, remediation campaigns that clear the most criticals/highs, a phased burn-down plan, and the riskiest workloads. Use this for any question about vulnerabilities, CVEs, image scanning or cluster security posture instead of reading VulnerabilityReport CRDs directly. If Trivy Operator is not installed the tool returns status='not_installed' with guidance to install the trivy-operator addon.

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_security_reports"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of priority CVEs to return (1-50). Defaults to 15.
severityNoFilter the priority CVE queue by minimum severity. Defaults to 'all'.all
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/5.0
Behavior3/5

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

It goes beyond the readOnlyHint annotation in two useful ways: it discloses that results depend on the Trivy Operator being installed and that the tool degrades to status='not_installed' with install guidance. It does not say anything about rate limits, data freshness, or whether results are cached, so the extra behavioural context is real but limited.

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?

The purpose is front-loaded in the first clause, followed by a compact enumeration of the returned sections. The single long sentence is dense but each listed item earns its place by telling the agent what it will receive from a tool that has no output schema.

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 describing return values, and it does so thoroughly, from severity breakdowns to remediation campaigns and the riskiest workloads. It also covers the missing-dependency edge case, leaving nothing an agent needs in order to call it correctly.

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 coverage is 100%, so limit, severity and cluster_id are already fully documented in the schema, including the enum values and defaults. The description only indirectly hints at the parameters by mentioning a 'prioritised queue' and 'severity split', which adds little beyond the schema's own wording.

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 gives a specific verb and resource ('Get the Trivy Operator image-vulnerability summary for the current cluster') and then enumerates what the summary contains, so the agent knows exactly what it retrieves. The Trivy/image-vulnerability scope also separates it from broader security siblings such as get_security_overview or list_security_findings.

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?

It states explicitly when to use it ('any question about vulnerabilities, CVEs, image scanning or cluster security posture') and names an alternative to avoid ('instead of reading VulnerabilityReport CRDs directly'). It does not, however, say how it differs from the other security-report tools in the sibling list, so the routing guidance is good but not complete.

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.