Skip to main content
Glama
Sentinel-One

Purple AI MCP Server

Official
by Sentinel-One

get_inventory_item

Retrieve detailed information about a specific managed asset in SentinelOne using its ID. Supports field filtering to get only the data you need.

Instructions

Get detailed information about a specific managed asset in SentinelOne by ID.

Use this tool to retrieve information about SentinelOne managed assets such as computers, servers, workstations, cloud resources, and network devices.

Args: item_id: The unique identifier of the inventory item. fetch_fields: Field filtering. Either: - Preset name: "MINIMAL", "STANDARD", or "ALL" (default: "ALL") * MINIMAL: 7 core fields (id, name, category, etc.) * STANDARD: 13 fields (MINIMAL + operational context) * ALL: All available fields (~200+ fields) - List of specific field names in camelCase: Examples: ["id", "name", "resourceType"] ["id", "osVersion", "ipAddress", "lastActiveDt"] Defaults to "ALL" to return complete asset information.

Returns: JSON string containing the requested fields (keys use camelCase format). Fields without values are excluded from the output.

Raises: ValueError: If item_id is invalid or empty, or fetch_fields is invalid. InventoryAuthenticationError: If authentication fails. InventoryNetworkError: If network operation fails. InventoryAPIError: If the API returns an error. InventoryClientError: For other client-level errors.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYes
fetch_fieldsNoALL

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/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 describes return format (JSON string), error types, and field exclusion behavior. It does not mention authentication or rate limits, but for a read-only tool, it's sufficiently transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with Args, Returns, Raises sections. It is front-loaded with the main purpose. Every sentence is informative and adds value, with no redundancy or fluff.

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 low schema coverage and presence of output schema, the description is comprehensive. It explains both parameters, return format, error types, and default behavior. It covers all relevant aspects for an agent to use the tool correctly.

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%, so description compensates fully. It explains item_id as unique identifier and fetch_fields in detail: presets with field counts, custom field list, default value, camelCase keys. Adds significant meaning beyond 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 'Get detailed information about a specific managed asset in SentinelOne by ID.' It uses specific verbs and resources, and distinguishes from sibling tools like list_inventory_items and search_inventory_items.

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?

The description explains what the tool does and the purpose of parameters, including presets. It implies usage for single-item retrieval but lacks explicit when-not-to-use or comparison with alternatives. Clear enough for an agent.

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