Skip to main content
Glama
Sentinel-One

Purple AI MCP Server

Official
by Sentinel-One
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

cve_search_by_id

Retrieve comprehensive CVE details including description, CVSS scores, affected products, and references by providing a CVE identifier.

Instructions

Get detailed information about a specific CVE by its identifier.

This tool queries the CVE database to retrieve comprehensive vulnerability information including description, CVSS scores, affected products, references, and remediation guidance.

What this tool provides:

  • CVE description and summary

  • CVSS v2 and v3 scores with vector strings

  • Affected products and versions (CPE format)

  • References to advisories, patches, and exploits

  • CWE (Common Weakness Enumeration) mappings

  • Publication and modification timestamps

  • Impact ratings and severity

Common Use Cases:

  • Security research and vulnerability assessment

  • Incident response investigations

  • Patch management prioritization

  • Security advisory creation

  • Compliance reporting

Args: cve_id: The CVE identifier in the format CVE-YYYY-NNNNN (e.g., CVE-2024-47176, CVE-2023-12345)

Returns: JSON string containing comprehensive CVE details including: - id: CVE identifier - summary: Vulnerability description - cvss: CVSS v2 score - cvss3: CVSS v3 score with full metrics - vulnerable_configuration: List of affected CPEs - references: Links to advisories and patches - cwe: Common Weakness Enumeration identifier - Published: Publication timestamp - Modified: Last modification timestamp

Examples: "CVE-2024-47176" - Recent vulnerability "CVE-2023-12345" - Search any CVE from any year "CVE-2021-44228" - Log4Shell vulnerability

Notes: - Data sourced from cve-search.org (CIRCL.LU) - No API key required - Database updated regularly from NVD and other sources - Returns detailed CAPEC, CWE, and CPE expansions

Not Found Response: When a CVE is not found, returns a JSON response with this structure: { "found": false, "resource": "CVE-YYYY-NNNNN", "resource_type": "cve", "message": "CVE-YYYY-NNNNN not found in the CVE database." }

Raises: CVEClientError: If there's an error communicating with the API (not for not-found cases).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cve_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

No annotations are provided, so the description carries full burden. It details data source (cve-search.org), auth requirements (no API key), update frequency, return structure, not-found response, and error handling. All behavioral traits are disclosed.

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 well-structured with clear sections, but it is somewhat verbose (e.g., bullet lists of return fields). It front-loads the main purpose and uses headings, which aids readability.

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?

Given the single parameter and rich output, the description covers input format, output structure, error cases, source attribution, use cases, and examples. Despite an output schema existing, the description adds valuable context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description adds complete parameter semantics: format (CVE-YYYY-NNNNN), examples, and explicit documentation in the 'Args' section. This fully compensates for the schema's lack of description.

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 starts with 'Get detailed information about a specific CVE by its identifier', which is a specific verb+resource combination. It clearly distinguishes from sibling tools like cve_search_by_vendor and cve_database_status through the focus on identifier-based lookup.

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?

Common use cases are listed (security research, incident response, etc.), but the description does not explicitly state when to avoid this tool in favor of alternatives like cve_search_by_vendor. The context is clear enough for typical usage.

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/Sentinel-One/purple-mcp'

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