Skip to main content
Glama

Get security finding

get_security_finding
Read-only

One security finding in full: the CVE with its exploitation intelligence (CISA KEV, EPSS), every current occurrence (cluster, namespace, workload, image, installed vs fixed version), and any matching disposition policies. Discover finding ids with list_security_findings. Read-only.

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": "get_security_finding"
  }
}

Input Schema

NameRequiredDescriptionDefault
finding_idYesFinding id (UUID) from list_security_findings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With readOnlyHint already declared, the description goes further and specifies the exact shape of the payload (CVE metadata, exploitation intel, all current occurrences, disposition policies), which is valuable since no output schema exists. It does not cover edge behavior such as what happens for an unknown or stale finding id, 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.

Conciseness4/5

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

Two tight sentences with the payload contents front-loaded and the id-discovery instruction last, so the reader hits the value proposition first. The trailing 'Read-only' duplicates the readOnlyHint annotation and is the only real redundancy.

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?

For a one-parameter read tool with no output schema and no nested objects, the description fully compensates by describing the returned content in enough detail that an agent knows whether this call answers its question. Nothing needed to call it correctly is missing.

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% and the single parameter's schema description already says it is a UUID from list_security_findings; the description's reference to the same discoverability path restates rather than extends that. Baseline 3 is appropriate since the schema carries the parameter semantics.

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 (retrieve one finding) and resource, then enumerates exactly what is included: CVE, exploitation intelligence (CISA KEV, EPSS), occurrences with cluster/namespace/workload/image and installed-vs-fixed versions, and matching disposition policies. This clearly separates it from list_security_findings (discovery) and list_security_finding_occurrences (occurrence listing).

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?

Explicitly routes the agent to list_security_findings to obtain the required id, which is the key prerequisite for calling this tool. It does not explicitly say when to prefer this over list_security_finding_occurrences or get_security_advisory, but the 'one finding in full' framing implies the drill-down use case adequately.

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.