Skip to main content
Glama
RedHatInsights

Red Hat Lightspeed MCP

Official

vulnerability__load_cve_dashboard

Read-only

Display CVEs across your account or for a specific system in an interactive dashboard with optional filters.

Instructions

Show, list, or display CVEs — account-level or for a specific system — in an interactive dashboard.

PREFER this tool over get_cves and get_system_cves whenever the user wants to see, show, list, or display CVEs, whether for the entire account or for a specific system. Use get_cves or get_system_cves only when you need the raw data for analysis or processing. The dashboard fetches data directly from the server. If system_uuid is provided, it fetches system-level CVEs. Otherwise, it fetches account-level CVEs. All filter parameters are optional.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort field. Use '-' prefix for descending.-cvss_score
limitNoMaximum number of CVEs to fetch.
impactNoComma-separated impact IDs (7=Critical, 6=High, 5=Important, 4=Moderate).7,6,5,4
offsetNoOffset for pagination.
cvss_toNoMaximum CVSS score filter.
filter_NoFull text filter for CVE name or description.
cvss_fromNoMinimum CVSS score filter.
system_uuidNoSystem UUID. If provided, fetches CVEs for this system. If empty, fetches account-level CVEs.
known_exploitNoFilter by known exploit (true, false, or true,false).true,false
advisory_availableNoFilter by advisory availability (true, false, or true,false).true,false
Behavior5/5

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

The description adds context beyond the readOnlyHint annotation by specifying it is an interactive dashboard that fetches data directly from the server, with no write behavior implied. No contradictions.

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 structured with a clear purpose statement, usage guidelines, and technical details. It is slightly redundant with schema but overall concise and well-organized.

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?

The description adequately explains input and behavior but does not mention return format or output details, which would be helpful given no output schema. The dashboard concept implies a list of CVEs but is not explicit.

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 parameters are already well-documented. The description adds no new semantic information beyond restating system_uuid behavior, which is already in the schema.

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 the tool shows, lists, or displays CVEs in an interactive dashboard, at account or system level. It explicitly distinguishes from sibling tools get_cves and get_system_cves by indicating this tool is for display and those are for raw data.

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?

The description explicitly says to prefer this tool over get_cves and get_system_cves for displaying CVEs, and to use those only when raw data is needed. It also explains behavior based on system_uuid parameter.

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