purple_ai_queryAsk SentinelOne Purple AI natural-language questions to investigate security alerts and retrieve AI-driven answers for faster SOC decisions.
Ask SentinelOne Purple AI a natural-language query. Uses Playwright headful; reuses browser session across calls.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| tenant | No | ||
| timeout_seconds | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses useful behavioral traits: it uses Playwright in headful mode and reuses the browser session across calls. However, with no annotations provided, it does not address authentication requirements, potential side effects, rate limits, or what happens when the session is stale, leaving significant behavioral gaps.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two short sentences with no filler. It front-loads the core purpose and then adds the most relevant implementation detail about browser session reuse, making every sentence informative.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description is too sparse for a stateful, browser-automated tool with a long default timeout and optional tenant parameter. It omits usage context, session prerequisites, and relationship to sibling tools like purple_ai_reset, even though an output schema may cover return values.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description adds meaning to the 'query' parameter by calling it a natural-language query, but it does not explain 'tenant' or 'timeout_seconds'. With 0% schema description coverage, the description only partially compensates for the missing parameter documentation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's action: asking SentinelOne Purple AI a natural-language query. It identifies the resource and the nature of the input, which distinguishes it from structured query tools like run_dv_query, though it does not explicitly name alternatives.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus siblings such as purple_ai_reset or refresh_login. The description implies it is for natural-language questions to Purple AI, but does not state prerequisites, exclusions, or how it relates to session management.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.