Skip to main content
Glama
RedHatInsights

Red Hat Lightspeed MCP

Official

vulnerability__get_cves

Read-only

Retrieve a list of CVEs affecting your account, including metadata and affected system counts. Use filters like CVSS score, impact, and known exploits to narrow results.

Instructions

Get list of CVEs affecting the account.

This provides an overview of vulnerabilities across your entire system inventory. Use this endpoint to get an overview of which CVEs are affecting your account, including some CVE metadata, how many systems are affected by each CVE, and more. For more info refer to OpenAPI spec

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filter_No
limitNoPagination - Maximum number of records per page.
offsetNoPagination - Offset of first record of paginated response.
sortNoAttribute sorting. Use `-` prefix to sort in descending order.-public_date
cvss_fromNoFilter based on cvss score, starting from the value.
cvss_toNoFilter based on cvss score, up to the value.
impactNoComma separated list of CVE Impact IDs. Example : 5,7. impact mapping: (0, 'NotSet'), (1, 'None'), (2, 'Low'), (3, 'Medium'), (4, 'Moderate'), (5, 'Important'), (6, 'High'), (7, 'Critical')1,2,4,5,7
rule_presenceNoComma seprated string with bools. If true shows only CVEs with security rule associated, if false shows CVEs without rules. true, false shows all.true,false
known_exploitNoString of booleans (array of booleans), where true shows CVEs with known exploits, false shows CVEs without known exploits.true,false
advisory_availableNoString of booleans (array of booleans), where true shows CVE-system pairs with available advisory, false shows CVE-system pairs without available advisory.true
affecting_host_typeNoComma separated string of values. Controls, whenever CVE has 1 or more affecting systems. Value "edge" returns CVEs with one or more vulnerable immutable systems, value "rpmdnf" returns CVEs with one or more vulnerable conventional systems. Value "none" returns CVEs not affecting systems of any kind. Allowed values: "edge", "rpmdnf", "none".rpmdnf

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already declare readOnlyHint=true, so no contradiction. The description adds context about the overview nature and included metadata but does not disclose behavioral traits like pagination behavior, rate limits, or side effects beyond what annotations provide.

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 description is three sentences long, front-loaded with the action. The first sentence is direct, but the second sentence is somewhat redundant ('overview' repeated). Overall concise, but slight redundancy prevents a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 11 parameters (all optional), an output schema exists, and annotations provide readOnlyHint, the description offers a high-level overview. However, it references the OpenAPI spec for more details, indicating incompleteness. It adequately covers the essential context but could be more comprehensive.

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 description coverage is 91%, meaning most parameters are well-documented in the schema. The description does not add significant detail beyond what is already in the schema parameters, so baseline score of 3 is appropriate.

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 'Get list of CVEs affecting the account,' specifying the verb and resource. It differentiates from sibling tools like vulnerability__get_cve (singular) and vulnerability__get_cve_systems (systems for a specific CVE), making it distinct.

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

Usage Guidelines3/5

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

The description provides context for when to use the tool ('to get an overview of which CVEs are affecting your account') but does not explicitly state when not to use it or mention alternatives. Sibling tool names imply differentiation, but no explicit guidance is given.

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/RedHatInsights/insights-mcp'

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