Skip to main content
Glama
Sentinel-One

Purple AI MCP Server

Official
by Sentinel-One

get_alert

Retrieve a specific alert's full details, including severity, status, assets, and analyst findings, using its ID.

Instructions

Get detailed information about a specific alert by ID.

Retrieves comprehensive alert data including metadata, timing information, severity, status, associated assets, and analyst findings.

Args: alert_id: The unique identifier of the alert (string).

Returns: Detailed alert information in JSON format containing: - id: Unique alert identifier - externalId: External system identifier (if any) - severity: CRITICAL, HIGH, MEDIUM, LOW, INFO, UNKNOWN - status: NEW, IN_PROGRESS, RESOLVED, FALSE_POSITIVE - name: Alert title/name - description: Detailed description of the alert - detectedAt: ISO timestamp when alert was first detected - firstSeenAt: ISO timestamp of first occurrence (if different) - lastSeenAt: ISO timestamp of most recent occurrence - analystVerdict: Expert analysis result (if available) - classification: Alert category/type - confidenceLevel: Detection confidence score - dataSources: List of data sources that contributed to detection - detectionSource: {product, vendor} information - asset: Associated asset information {id, name, type} - assignee: Assigned user information {userId, email, fullName} - noteExists: Boolean indicating if notes are attached - result: Investigation outcome - storylineId: Associated storyline identifier - ticketId: Associated ticket identifier

Common Use Cases: - Incident investigation and triage - Alert enrichment with contextual data - Status and assignment tracking - Evidence collection for security workflows

Raises: RuntimeError: If there's an error retrieving the alert. ValueError: If alert_id is invalid or empty.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
alert_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries the full burden for behavioral transparency. It mentions possible exceptions (RuntimeError, ValueError) but does not disclose whether the operation is read-only, idempotent, or any side effects. This is adequate but not comprehensive.

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 sections (Args, Returns, Common Use Cases, Raises) and front-loads the key purpose. Some verbosity exists, especially in the returns section which lists many fields, but it is organized and readable.

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?

Despite having only one parameter, the description provides extensive return field documentation and common use cases. The output schema likely covers the return structure, so the description complements it fully. Context is complete for this tool's intended use.

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

Parameters2/5

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

The description defines alert_id as 'The unique identifier of the alert (string)', which adds minimal semantic value beyond the schema type. With 0% schema description coverage, the description should compensate, but it only restates the parameter name and type without examples or format details.

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 retrieves detailed information about a specific alert by ID. It distinguishes from siblings like list_alerts, search_alerts, get_alert_history, and get_alert_notes by focusing on a single alert's comprehensive data.

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 provided (incident investigation, enrichment, tracking, evidence collection), giving clear context for when to use this tool. It does not explicitly mention when not to use it or alternatives, but the sibling tools (list_alerts, search_alerts) are sufficiently differentiated by the description.

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