Skip to main content
Glama

List security finding occurrences

list_security_finding_occurrences
Read-only

List where one security finding occurs: every cluster, workload, container and image the CVE is observed on, one row per occurrence, with its scan state (active or resolved), disposition and first/last seen. Read-only. get_security_finding embeds the current occurrences; use this to page through them, to narrow to one cluster, or to see the resolved ones (status=resolved) the detail hides.

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": {
      "finding_id": "<finding_id>"
    },
    "name": "list_security_finding_occurrences"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1.
statusNoOne occurrence state: open, acknowledged, accepted_risk or resolved. Omit for the active set.
page_sizeNoResults per page (default 50).
providersNoOnly occurrences of findings from these providers: trivy_operator, node_kernel, node_packages or samma. A finding has one provider, so naming another answers an empty page.
cluster_idNoRestrict to one cluster (UUID).
finding_idYesFinding id (UUID) from list_security_findings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / providers / description
      Previous value: -"Only occurrences of findings from these providers: trivy_operator, node_kernel or samma. A finding has one provider, so naming another answers an empty page."New value: +"Only occurrences of findings from these providers: trivy_operator, node_kernel, node_packages or samma. A finding has one provider, so naming another answers an empty page."
  2. Changed1 schema field changed
    • addedInput schema / properties / providers
      Added value: +{
      +  "description": "Only occurrences of findings from these providers: trivy_operator, node_kernel or samma. A finding has one provider, so naming another answers an empty page.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  3. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the 'Read-only' sentence is mostly redundant. Beyond that, the description discloses the result grain ('one row per occurrence'), the fields each row carries, and that status=resolved surfaces rows the detail view hides – useful context the annotations do not provide. Pagination totals and sort order are not described, which keeps it from a 5.

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?

Three sentences, front-loaded with the verb and result shape, then the alternative and the three use cases. No filler; the only near-redundancy is the short 'Read-only' clause, which costs little.

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?

There is no output schema, yet the description states the row grain and the columns an agent will get back, covers read-only safety, and routes to the alternative tool. For a six-parameter paginated list tool this is complete enough to call correctly.

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 real meaning beyond the schema by explaining why one would set status=resolved (the detail view hides resolved occurrences) and that cluster_id is for narrowing. It does not touch page/page_size, but the schema already handles those adequately.

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?

States a specific verb and resource ('List where one security finding occurs') then enumerates the dimensions returned: cluster, workload, container, image, scan state, disposition, first/last seen. It explicitly contrasts with the sibling get_security_finding, so an agent can distinguish the two without opening either schema.

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?

Gives three concrete selection conditions – page through occurrences, narrow to one cluster, see the resolved ones the detail hides – and names the alternative (get_security_finding) that embeds the current occurrences. Nothing is left to inference about when to prefer this tool.

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.